turminal

15 ms·

151.
by turminal 5y ago
Prioritizing your market share over private gains of your users is precisely the thing that makes you "not an ally of user freedom"
152.
by turminal 5y ago
The closed system is just fancy words for "you don't really own your phone, we do". Doesn't help a tiny bit against the devices getting pwned, if you'll excuse the pun.
153.
by turminal 5y ago
You're saying this as if you're very convinced it's a bad thing. Why? I'm not so sure it's a bad thing.
154.
by turminal 5y ago
Lack of incentive contributes a great deal to lack of quality. If the company knows they are going to lose money if they are careless, they'll be less careless. Way too many bugs and security vulnerabilities are consequences of nothing
155.
by turminal 5y ago
> It has precisely copied the original API, despite the fact the original API is quite unidiomatic in the new language. STL isn't even idiomatic in C++ ;)
156.
by turminal 5y ago
We can only speculate, but it's very unlikely this had anything to do with how good minix is.
157.
by turminal 5y ago
The name is irrelevant, the point is that it's a blatant lie.
158.
by turminal 5y ago
More bloated != more lines of code
159.
by turminal 5y ago
> If you wanted readability, or maintainability you have to sacrifice performance. If you want performance, you have to sacrifice everything else. This is true in every programming language to some extent. What makes it worse in C++ is t
160.
by turminal 5y ago
Github is not their own server.
161.
by turminal 5y ago
For better of for worse, wordpress can at this point be considered critical infrastructure.
162.
by turminal 5y ago
> This isn’t about JS. That's precisely why it shouldn't be in JS. Edit: to clarify, javascript is full of random warts that you have to know about in order to use it effectively, that's why I think a language with less su
163.
by turminal 5y ago
It didn't become widely used because it were any good and being widely used generally doesn't imply quality. I think the decision on what language to use in teaching material should be made based on quality and ease use, not popul
164.
by turminal 5y ago
This is the wrong kind of approachable, because you have to learn a ton of random web things before you do anything outside the repl and before your program can even process user input and then people struggle with those two concepts that w
165.
by turminal 5y ago
Pretty much everything is in conflict. POSIX standarized and attempted to unify a dozen different incompatible systems that developed independently on top of the original unix from bell labs. Those systems were developed by building new fun
166.
by turminal 5y ago
All in the name of "security" of course.
167.
by turminal 5y ago
No, at least not in any way we know about. I was caused by violent volcanic activity which is governed by forces from the earth's interior.
168.
by turminal 5y ago
Have you read the article? It doesn't look like you did.
169.
by turminal 5y ago
> Makes a lot of sense for competitors to be in the Fediverse. Or maybe not. Maybe code hosts and forges should just be code hosts and forges and I don't think embracing github's model is a good idea. Edit: I wish cooperability
170.
by turminal 5y ago
Iran happens to sit on enormous amounts of oil. Energy being cheap there is hardly a surprise.
171.
by turminal 5y ago
I feel like vim should really be focusing on other, less shiny things. Users that primarily want a shiny editor are already using VS code and the like.
172.
by turminal 5y ago
Coincidentally, both green energy advocates and Rust advocates tend to have fairly naïve expectations. I consider myself a green energy advocate and would be glad to see c++ go away but I find naïveté a huge obstacle on the path to both of
173.
by turminal 5y ago
C knowledge is still way more generally useful than javascript and/or web knowledge. Whatever you think of C there's no denying it's everywhere and understanding it is relevant in pretty much every software system in existenc
174.
by turminal 5y ago
C++ is not going away in the foreseeable future, like it or not.
175.
by turminal 5y ago
It's interesting that the author doesn't like the complexity of kubernetes, but it appears they love complexity in the languages they use.
176.
by turminal 5y ago
> But the Kubernetes riff was telling: when using a cloud provider, so much of the sustem management is provided. Way too much for most usecases out there. And if you don't understand it, you can't fix it when it breaks.
177.
by turminal 5y ago
That would work just fine with a string comparison.
178.
by turminal 5y ago
There's QBE ( https://c9x.me/compile ). It's tiny compared to LLVM and only does the most impactful optimizations, but it's also much simpler to work with. A small but dedicated community of language builders
179.
by turminal 5y ago
> GCC itself also doesn't have full support for c11 yet. Neither do other, much better funded compilers, to be fair.
180.
by turminal 5y ago
Unfortunately you probably daily rely on multiple 32-bit linux machines, most of the time not realizing you do. I agree this should be mentioned in the title though.

More ›