Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
Subsentient
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
10 ms
·
61.
▲
by
Subsentient
5y ago
Rust must stabilize its ABI if it seeks to be a useful systems language. You usually don't have to worry about ABI for LLVM and GCC interaction, so why should you need to worry about rustc and gccrs interaction? C++ STL and MSVC are kn
62.
▲
by
Subsentient
5y ago
All I'm gonna say is that as far as problems go, this one isn't so bad. I wonder what percentage of those kids were already nearing obesity. I guess I can take comfort in the fact that having kids with a little extra chönk isn
63.
▲
by
Subsentient
5y ago
Among other things, async was done quite poorly imho and I know I'm not the only one to think so, and a huge pet peeve of mine is how rustc prevents you from turning off specific optimizations when they can be harmful to your code, e.g
64.
▲
by
Subsentient
5y ago
There are also those of us who are thrilled that a total alternative Rust parser is being written. A systems language should never be centralized to the degree Rust is.
65.
▲
by
Subsentient
5y ago
Indeed, C++ has benefited enormously from having multiple implementations. If one compiler produces results different from another, generally speaking, you've just found an issue in that compiler. The multiple implementations serves as
66.
▲
by
Subsentient
5y ago
And if you disagree with the unilateral decisions of the rustc developers? "Go fork it or write your own"? Yeah that's what we're doing. Don't be surprised when what was often a taunt in Rust-related arguments actua
67.
▲
by
Subsentient
5y ago
I have literally had to read compiler source code to find out Rust behavior before, more than once . That should never happen. The more implementations of a language there are, generally speaking, the better understood a language is. C++
68.
▲
by
Subsentient
5y ago
Well for me personally, a big part of it is a conscious desire to reduce the unilateral control that the Rust Foundation and core rustc developers have over the language. I find some of their decisions actively harmful for a systems languag
69.
▲
by
Subsentient
5y ago
I'm self-taught, been doing this since I was 13. As far as how I am as a programmer, the way I turned out was rigid in my design patterns, but with I'm told unusually readable code. My biggest sin is a lack of comments and documen
70.
▲
by
Subsentient
5y ago
static const char StringLiteral[] = "hello world"; std::vector<char> Derp; Derp.resize(sizeof StringLiteral); memcpy(Derp.data(), StringLiteral, sizeof StringLiteral);
71.
▲
by
Subsentient
5y ago
An innovative new STL with unlockable features, such as: std::vector: $5 std::string: $15 std::map: $30 std::unordered_map: $100
72.
▲
by
Subsentient
5y ago
Bleurgh. I have a deep soft spot for C, and I'm known to get twisted pleasure from using obscure language features in new ways to annoy people, but this is a level of abuse that even I can't get behind. If you need namespacing, us
73.
▲
by
Subsentient
5y ago
I agree with you, though sadly HN doesn't. Some days you're just beating your skull against a brick wall recompiling 3rd party libraries till 5pm, some days you get to write the big exciting part. That's life. That's the
74.
▲
by
Subsentient
5y ago
Yeah that's a whole nother can of worms for me with Rust, something that pisses me off a lot. By enforcing strict aliasing with no way to disable, Rust is making unsafe code intrinsically more unsafe , because you can't get predi
75.
▲
by
Subsentient
5y ago
Both, though mostly documentation. To me, a standard is the documentation. The fact I have to read rustc source to find syntax is frankly an abomination. A standard defines syntax and grammar in ways that a html reference page never doe
76.
▲
by
Subsentient
5y ago
Other than being proprietary, macOS is definitely much better than Windows. The problem is that macOS requires Apple hardware, which has been dog shit for years now.
77.
▲
by
Subsentient
5y ago
Yeah, but less likely frankly, because it's less likely the malware author would take the time to make a ransomware for Linux, though I know it's happened before. 1% of the market vs 80% of the market, which would you target? And
78.
▲
by
Subsentient
5y ago
Ahh, well no. I don't think Windows users are idiots. I think they're normal, non-technical people who don't want to drop to a terminal to pair their bluetooth earbuds because the BlueZ GUI was written in an afternoon by some
79.
▲
by
Subsentient
5y ago
You'll keep thinking that until you pirate a copy of Adobe Shitware 2077(tm) and it works fine for a day until the embedded cryptolocker activates and holds everything on your system hostage for 3 bitcoin.
80.
▲
by
Subsentient
5y ago
Windows is the dominant operating system, and as such has a giant target on its back. It's true, I despise Windows, but the risk of torrenting on Linux vs the risk of torrenting on Windows is quite a huge difference. And look, Microsof
81.
▲
by
Subsentient
5y ago
Both. Plenty of malware-infested executables in torrents.
82.
▲
by
Subsentient
5y ago
These issues cannot be fixed by merely updating the docs for a few items. (and frankly I don't contribute much to big FOSS projects because I've had bad experiences with big projects before) This can only be fixed by A. Requirin
83.
▲
by
Subsentient
5y ago
No, I'm definitely on the right language. For example, lots of magical implicit reborrows with fuck all in the documentation, pattern matches and specifiers with no formal behavior defined, lints that change constantly. I do use nightl
84.
▲
by
Subsentient
5y ago
Well you'd really have to be crazy to try and torrent stuff on a Windows machine nowadays anyways. That's just getting on your knees and begging for malware. Maybe this will help some of the more savvy users realize that Windows s
85.
▲
by
Subsentient
5y ago
The problem with analyzing stuff like this about Rust, is that even Rust itself has no idea how it works, or what syntax and semantics actually mean. Rust doesn't merely lack a language standard, its reference and advanced documentatio
86.
▲
by
Subsentient
5y ago
Well, seeing as 5G is currently a cat diarrhea smoothie, probably a while. It's literally better to just use LTE in most cases. I get the feeling LTE will be around and supported for a long time to come.
87.
▲
by
Subsentient
5y ago
Ditto. Cool project, but when I saw it was written in JS, a wave of disgust washed over me.
88.
▲
by
Subsentient
5y ago
Please no. ARM chips are a nightmare enough for compatibility on phones and tablets, even devices several years old. I don't want to need custom patched Linux kernels just to boot my fucking laptop! Oh but I already know. That's d
89.
▲
by
Subsentient
5y ago
Hardly seems draconian considering GNU has a copyright surrender requirement, and most large FOSS projects have style requirements.
90.
▲
Show HN: Volition: open-source remote access tool
(github.com)
2 points
by
Subsentient
5y ago
|
4 comments
More ›