teacup50

12 ms·

61.
by teacup50 10y ago
> There's plenty of gray area ... There's not. Journalism and politics have this covered: NO GIFTS. It's really that simple.
62.
by teacup50 10y ago
Your own release notes contain descriptions of breaking language changes. That may change as the language matures -- great. I keep an eye on Rust so that I can eventually try actually using it for kernel-level development work.
63.
by teacup50 10y ago
> Which means Swift, .NET Native, Java/C++, C++17, on the OSes from Apple, Google and Microsoft. You've seen where their OS code comes from, and what it's written in, right? Just to be very clear, I'm very well-ve
64.
by teacup50 10y ago
> I would like to see an example of a legitimate Linux Kernel module written in Rust that is in some form of use. Seriously this. I write an awful lot of kernel code. There's absolutely no way I'd try to convince folks to acc
65.
by teacup50 10y ago
Given the litany of deprecation markers applied to existing APIs, one must presume the intention of removing them, no?
66.
by teacup50 10y ago
> This is completely false. Do you have an example? Review the "Breaking Changes" of release notes, and the number of discussions regarding removing API after a short (in the view of someone who works on said "systems
67.
by teacup50 10y ago
"Trivial to upgrade" is not the same as stable. It means code bitrots in-place.
68.
by teacup50 10y ago
Among other things, systems programming projects generally require stability of language syntax, API, and ABI. In terms of ABI stability, Rust has none. In terms of API stability, they seem willing to drop features within a major release cy
69.
by teacup50 10y ago
Of course, their triggers tend to be things like loud noises, not ideas they disagree with or words they find scary.
70.
by teacup50 10y ago
Protesting the speaker's ideas is always fine. Protesting the speaker's existence is difficult to intellectually justify as a healthy exchange of ideas, including critique. These days, what we see is a lot of the latter -- up
71.
by teacup50 10y ago
> That's an ideal that was never really true. Sure it was. In the 1960s and 70s, for example, when Universities were a hotbed of free speech and civil liberty activism: https://en.wikipedia.org/wiki/Free_Speech_
72.
by teacup50 10y ago
> This turned out to be caused by HTTP/2.0 which only allows 1 billion streams over a single connection. Hilarious. People called this issue out as an obvious flaw when HTTP/2.0 was first proposed, got ignored, and here the i
73.
by teacup50 10y ago
No, it matters. Inefficiency adds up, and CPU cycles you waste on useless overhead aren't available to spend on something that actually matters -- like Garbage Collection.
74.
by teacup50 10y ago
> If you don't want that, go ahead and just write raw bytes and don't bother with the serialization layer. Or just keep using protobuf2, 'cause it's been working great for us for ~6 years. > But you don't h
75.
by teacup50 10y ago
> You always had to check the individual fields for the zero value. No, you didn't. A required field has a value, period. If it defaults to a particular value, then that's the value it has. If you had a non-required field, th
76.
by teacup50 10y ago
> A canonical example is that you add a required field ... Yeah. Don't do that without versioning your protocol. It's even less difficult to handle than maintaining API/ABI compatibility in a library. > So practicall
77.
by teacup50 10y ago
What do you need me to clarify?
78.
by teacup50 10y ago
> - removing optional values is actually quite nice. In practice, I end up checking for "missing or empty string" anyway. I feel the opposite; this greatly reduces the utility of protobuf. Previously, I could trust that if pa
79.
by teacup50 10y ago
What if you believe the tautological kernel at the core of Marxism is what causes communism ("as implemented") to always run off the rails, and become an oppressive authoritarian state? What I see is the root of Communism; &qu
80.
by teacup50 10y ago
Spend some time out of a city. Or at least trying to consider what life is like outside of a city.
81.
by teacup50 10y ago
There are basically three major classes of Java code execution bugs: 1) Bugs in native code (generally image processing, compression, etc). This code tends to be derived from existing libraries, and so shares common vulnerabilities. 2) Bugs
82.
by teacup50 10y ago
We got hosed by PADL and rfc2307/rfc2307bis. In short: We never standardized a viable schema that covered the majority of real-world enterprise use-cases. Active Directory did. We got stuck with the broken rfc2307 (essentially NIS-in-L
83.
by teacup50 10y ago
LDAP/AD is neither insecure nor obsolete. Using a 3rd-party cloud-based service to manage server authentication, SSH keys, et al, seems insanely insecure however -- especially when your alternative is simply running LDAP locally.
84.
by teacup50 10y ago
OpenSSH now also supports external authorized_key handling via AuthorizedKeysCommand, and thus simple integration with LDAP: https://github.com/AndriiGrytsenko/openssh-ldap-publickey
85.
by teacup50 10y ago
I'd love it if the FCC mandated that the streaming video services provide a common standard that allowed me to, for example, watch Netflix, Amazon, and Apple iTunes, all in one application. As a consumer, that would be a win. As a deve
86.
by teacup50 10y ago
I agree with most of your points, but disagree strenuously with this one: It's 2016, and these dead, flat, static PDFs are functionally identical to the paper they replaced! There's a lot of value in static PDFs and how we forma
87.
by teacup50 10y ago
Depending on which workstation I'm using, I've got anywhere from 6880x1440 to 7680x1440 worth of pixels in front of me. Still prefer physical reference books. Note that I'm not referring to API or library documentation; that&
88.
by teacup50 10y ago
I'm not so convinced it's obsolete. I read all my fiction digitally, sure, but for technical/reference books, nothing has yet beat the UX of a paper book, and I'm unconvinced that anything in the near term future ever
89.
by teacup50 10y ago
Apple? They're the people that shipped transparent CPU emulation mechanism to keep their ABI working and avoid breaking customers. Twice.
90.
by teacup50 10y ago
If that's your definition, then FreeBSD and Solaris solved this without paying the systemd tax, via ZFS-based boot environments. https://www.freebsd.org/cgi/man.cgi?query=beadm&sektion=&man... NeXt->App

More ›