dispose13432

9 ms·

31.
by dispose13432 10y ago
>As a total beginner (learning programming by myself since 2 or 3 years), i am always asking myself, how often "little" things like race conditions break something in production Rookie mistake (and a shoot-yourself-in-the-foot-
32.
by dispose13432 10y ago
> re: generics: If they aren't implemented carefully, they could unacceptably complicate the language. Can you explain why? For example, simple generics which could be implemented as regex doesn't seem to complicated? Am I miss
33.
by dispose13432 10y ago
>Companies have far too much internal plumbing to permit browsers to auto-update themselves. Being feature-compatible with the latest SV-poster-child website is insignificant compared to maintaining stability for the tax-management team&
34.
by dispose13432 10y ago
>I'm of the opinion that there is an infinite amount of jobs; as we as a species always want our current situation to be better than it currently is One of the unspoken problems with the tech revolution is that there are a lot of pe
35.
by dispose13432 10y ago
>There are no final variables in Go. const?
36.
by dispose13432 10y ago
>Because those communities, logically due to the UNIX influence, are biased towards C. Not Linux (Warning: Typical Linus rant - http://harmful.cat-v.org/software/c++/linus ).
37.
by dispose13432 10y ago
>Take a guess which strategy makes junior developers write better code. An org can mandate use of only safe pointers.
38.
by dispose13432 10y ago
C++ can be safe. Just use only safe pointers and vectors. The thing is that rust does two things: 1. Safety 2. FP style code ("magic") I wouldn't mind #1, but #2 kind of turns me off.
39.
by dispose13432 10y ago
>I don't even understand why you'd want to remove functional programming from a low level language like Rust Because I want a simple to read language? It's not all about performance. C++ doesn't have bad performance a
40.
by dispose13432 10y ago
>unwieldy and slow So force one to do it consciously (kind of like unsafe).
41.
by dispose13432 10y ago
>Something like threading race conditions is a real problem, but not easy to fix. It is. It's called channels.
42.
by dispose13432 10y ago
Well, that's an "easy" bug. What about not-shadowing a "non-loop" variable? Take a look at this question: http://stackoverflow.com/questions/18499352/golang-cuncurren... It's easy to
43.
by dispose13432 10y ago
That's one thing I hate about Go, is how easy it is to shoot yourself in the foot with it. Really, it has a decent way to manage inter-thread communication - channels. But the language still permits me to read/write a "non
44.
by dispose13432 10y ago
You know what I would like? (Yeah, speaking of entitlement :) ) A "safe C". No classes, no functional programming (except function pointers, maybe anonymous functions), no exceptions, just plain C but 1. memory safe 2. optional a
45.
by dispose13432 10y ago
http://arstechnica.com/gadgets/2012/09/google-blocked-acers-... So Amazon can't get Acer to build them phones or tablets. As most independent manufacturers build Android phones, Amazon had a hard time fi
46.
by dispose13432 10y ago
Don't let perfect be the enemy of good enough. While most people run Android the same way people run Apple, you can run Android and get your apps from f-droid, and you can run CM (and, if your into these things, Xprivacy), so while
47.
by dispose13432 10y ago
True!! I thought they were aquihired by OnePlus after the CM deal fell through to make OxygenOS
48.
by dispose13432 10y ago
> Closed source apps are not the threat > Yes, they are. See > https://www.gnu.org/philosophy/shouldbefree.html Well, they should. But I wouldn't call a closed-source messaging app (which you can replace
49.
by dispose13432 10y ago
> "Android" per-se is Apache 2, i.e. free to use without restrictions (thus Amazon's "Fire OS"). That's why I stressed "in a factory". No factory which makes commercial Android is permitted to make
50.
by dispose13432 10y ago
The article is wrong on so many counts: 1. Closed source apps are not the threat (Nowhere does it say that the dialer, home screen, messaging app, or camera are a part of the OS. All are replaceable, and all replacements integrate just as w
51.
by dispose13432 10y ago
We'll see in a few months how viable is it.
52.
by dispose13432 10y ago
AOKP - dead. PA - dead AOSB - Exceeded bandwidth and archive doesn't seem to have archived it properly. According to Google cache, they're working on L, so seems dead. Slim - was dead for a few years. Seems to have revived. The qu
53.
by dispose13432 10y ago
>I don't hear much about performance problems causing major trouble in popular software and making everyone patch things in haste. How did nginx unseat apache?
54.
by dispose13432 10y ago
>Many popular languages nowadays essentially have just one viable open source toolchain: Go has the Go toolchain (gccgo being niche), Python 3 has CPython (Jython and IronPython only support Python 2.7, and PyPy is not up-to-date), Swift
55.
by dispose13432 10y ago
The question is not so much how many working compilers are there, but how many rely on the language. Practically, PHP has one interpreter, but if they go out, you can be assured that someone will fork and maintain it. On the other hand, if
56.
by dispose13432 10y ago
>That argument seems akin to avoiding C# because only MS supports it Or avoiding Flash because only Adobe supports it, or SilverLight/VB because only MS supports it, or Objective C because only Apple supports it.
57.
by dispose13432 10y ago
>On similar note, why Rust over Go? I was going to say that rust has performance advantages over Go (due to GC), but look at benchmarks: http://benchmarksgame.alioth.debian.org/u64q/compare.php?lan... Go wins some a
58.
by dispose13432 10y ago
It's an unfortunate situation, but the way _they_ put it (two sides to every fight) is that they don't know if he'll drop out in a week and all those who downloaded it will come screaming "Were's our updates!!"
59.
by dispose13432 10y ago
They have one. It's called LineageOS.
60.
by dispose13432 10y ago
They were the darling of custom ROMs before Cyanogen Inc. When they incorporated, a lot of people hoped it would help sponsor development (while others, suspecting what would happen, forked into OmniRom). Unfortunately, once they incorporat

More ›