|
yo, just use whatever memory you need to make performance reliably quick, don't leak, and stick each unit of work in its own thread. chances are nothing you do will ever be affected by the mythological gc pausing problem. guis in android Linux are bad because: bad hardware, bad programmers, bad jvm.
|
# ? Apr 7, 2014 15:36 |
|
|
# ? Jun 7, 2024 21:10 |
|
shaggar was right
|
# ? Apr 7, 2014 15:49 |
|
MeramJert posted:shaggar was right
|
# ? Apr 7, 2014 15:54 |
|
Cybernetic Vermin posted:the perfection of gc is one of those slightly annoying nerd myths that i think mostly exists because people like absolutes, when very few absolutes exist. gc is deeply flawed, and has the very distinct downside of being an all-or-nothing proposition if it is to work well and be easy to work with. pretty clearly desirable for robust software, but a source of many problems and often not at all desirable. the situation you call out as ideal — monomorphic data referenced from a unique location — has most of the guarantees necessary to inline storage into the "container", which is (1) generally a superior design for performance and (2) a feature of quite a number of languages already. external tagging alone can be done in a slightly broader set of cases because inlined storage requires a non-recursive type, but i think you'd agree that that's not in the interesting subset it's very difficult to do even external tagging implicitly in most OO languages, though, because you have to prove that the object is never used polymorphically (including by the GC if applicable, and designing the GC metadata to express specific types instead of just object/non-object makes GC much more expensive). you can do it with user annotations that say that the type isn't polymorphic, ofc, but once you've got that, you should really just go the step further and make the annotations inline the storage
|
# ? Apr 7, 2014 17:38 |
|
Shaggar posted:yo, just use whatever memory you need to make performance reliably quick, don't leak, and stick each unit of work in its own thread. chances are nothing you do will ever be affected by the mythological gc pausing problem. This sounds about right. I cannot imaging GC being so bad that it needs to stop the entire machine for several seconds. Are they passing around a global array/hash so big that the OS starts loading it to virtual memory?
|
# ? Apr 7, 2014 19:25 |
|
I think that's how p-lang development is done
|
# ? Apr 7, 2014 19:27 |
|
MeruFM posted:This sounds about right. in the days of jdk 1.0, it could definitely happen
|
# ? Apr 7, 2014 19:29 |
|
Mr Dog posted:well you can always just write native code on Android, though the user interface APIs are all Java-only so you have to have at least some Java in your app. you can actually do Native Activities in Android apps since 2.3, which covers ~99% of android users.
|
# ? Apr 7, 2014 19:45 |
|
Shaggar posted:I think that's how p-lang development is done
|
# ? Apr 7, 2014 22:07 |
|
Shaggar posted:that's how p-lang development is done
|
# ? Apr 8, 2014 00:19 |
|
Shaggar posted:development is done
|
# ? Apr 8, 2014 01:37 |
|
Shaggar posted:that's how
|
# ? Apr 8, 2014 01:51 |
|
javascript is a truly great languagecode:
|
# ? Apr 8, 2014 04:12 |
|
you could have picked an actual bad example. that's the behavior you'd expect. or do you think ~5 should return 0x...FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFA?
|
# ? Apr 8, 2014 04:49 |
|
shrughes posted:you could have picked an actual bad example. that's the behavior you'd expect. or do you think ~5 should return 0x...FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFA? Python code:
|
# ? Apr 8, 2014 05:31 |
|
2147483648 & 2147483649 -2147483648 ~5 -6
|
# ? Apr 8, 2014 05:34 |
|
something something type promotion|coercion|im gay
|
# ? Apr 8, 2014 05:35 |
|
the main problem with 32-bit signed bitwise ops is that it encourages the development of javascript crypto
|
# ? Apr 8, 2014 07:15 |
|
otoh the prevailing cryptos appear to be written in c with the expected results ffs theo, we are not about to put up with your shithead ways if your software isn't secure
|
# ? Apr 8, 2014 08:09 |
|
More new features going into C#, because you asked: (not sold on the $butt garbage, though) https://roslyn.codeplex.com/wikipage?title=Language%20Feature%20Status&referringTitle=Documentation Also http://msdn.microsoft.com/en-US/vstudio/dotnetnative Microsoft owns, hail Satya(n)
|
# ? Apr 9, 2014 04:18 |
|
i don't get how .NET Native differs from NGen. I do, however, look forward to the massive speed boost/memory gains in all of our server code. for free. dictionary initializers look awful using static members is cute. it's almost like non-member functions with namespaces! but everything is still an object you guys
|
# ? Apr 9, 2014 04:29 |
|
binary literals? about loving time! why are binary literals restricted to being like... a gcc non-standards tihng
|
# ? Apr 9, 2014 05:58 |
|
Bloody posted:binary literals? about loving time! why are binary literals restricted to being like... a gcc non-standards tihng Erlang has them with pattern matching Go on wikipedia or a RFC and just dump the spec directly in there. code:
|
# ? Apr 9, 2014 11:39 |
|
whoa
|
# ? Apr 9, 2014 11:42 |
|
|
# ? Apr 9, 2014 13:47 |
|
Cybernetic Vermin posted:otoh the prevailing cryptos appear to be written in c with the expected results youve got to be loving kidding me and of course i had to learn it from yospos first
|
# ? Apr 9, 2014 16:41 |
|
qwerasdf posted:More new features going into C#, because you asked: (not sold on the $butt garbage, though) i wish there were more examples for those new features also i will suck a hobos dick if it gets that ?. operator into the spec Kuvo fucked around with this message at 17:34 on Apr 9, 2014 |
# ? Apr 9, 2014 17:29 |
|
Kuvo posted:i wish there were more examples for those new features um excuse me it should actually be written as >>=
|
# ? Apr 9, 2014 17:42 |
|
shrughes posted:the main problem with 32-bit signed bitwise ops is that it encourages the development of javascript crypto you know, you can do bigint arithmetic just fine with floats.
|
# ? Apr 9, 2014 20:30 |
|
Kuvo posted:also i will suck a hobos dick if it gets that ?. operator into the spec aaa that's such a good idea i haven't wanted something in php so bad since short array syntax
|
# ? Apr 9, 2014 20:33 |
|
what's the thread oponion on haxe did anybody ever use it in a real thing, if so how was it?
|
# ? Apr 9, 2014 23:32 |
|
AlsoD posted:um excuse me it should actually be written as >>= yeah csharp already has monad syntax it's called linq or use fsharp
|
# ? Apr 9, 2014 23:47 |
|
Malcolm XML posted:yeah csharp already has monad syntax it's called linq you can't use linq for possibly-null objects or futures though right, isn't linq for streams only?
|
# ? Apr 9, 2014 23:53 |
|
Kuvo posted:i wish there were more examples for those new features Granted http://stackoverflow.com/questions/22881465/what-do-these-new-c-sharp-6-features-do/22881736#22881736
|
# ? Apr 10, 2014 00:51 |
|
This week in Stupid C# Trickscode:
|
# ? Apr 10, 2014 09:29 |
|
coding horrors thread is currently defending JS automatic semicolon insertion
|
# ? Apr 10, 2014 10:44 |
|
AlsoD posted:you can't use linq for possibly-null objects or futures though right, isn't linq for streams only? iirc fsharp implements options as a special type that uses null as nothing
|
# ? Apr 10, 2014 11:23 |
|
Edit: double posting phone
Maluco Marinero fucked around with this message at 11:39 on Apr 10, 2014 |
# ? Apr 10, 2014 11:37 |
|
coffeetable posted:coding horrors thread is currently defending JS automatic semicolon insertion Of all the JS features for COBOL posters to un-ironically defend, automatic semicolon insertion would be the last thing I'd think of.
|
# ? Apr 10, 2014 11:38 |
|
|
# ? Jun 7, 2024 21:10 |
|
a lot of the js hipster types will defend ASI saying the rules are simple and that semicolons make their code look all dirty and unclean. you should just learn the rules and not make mistakes of missing them anywhere, ever. i believe the npm codebase in node is full of terrible stuff like this. they also do variable declarations/arrays like so: code:
|
# ? Apr 10, 2014 17:46 |