Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
heja_bruh
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
5 ms
·
1.
▲
by
heja_bruh
9y ago
What makes you think I'm trolling? Honestly, I'm tired of all these mediocre devs just pushing their keyboards in some inefficient, unsafe language and are totally unaware of the alternatives. If I'm showing them a greater al
2.
▲
by
heja_bruh
9y ago
You should definitely try rust, it's better than its counterparts, rapidly growing, memory safe language with utmost priority on efficiency. Plus its cross-platform too :)
3.
▲
by
heja_bruh
9y ago
Rust has good IDE support, graphical debuggers are around the corners, gui toolkits are coming and compile times are improving. By the time 2017 ends, rust will improve on all these things, while .NET platform will still be stuck with a slo
4.
▲
by
heja_bruh
9y ago
The big 4 are already using rust in various internal projects (including Microsoft). This comment just shows that you're afraid your job will be taken up by one of the rust devs in future..
5.
▲
by
heja_bruh
9y ago
> Are you telling me that a Rust code base with over 100 devs won't have any problems If you've had 100 problems writing c++, rust will reduce 99 of them. No data races, no SEGFAULTS - yes its impossible, no pointer mathematics
6.
▲
by
heja_bruh
9y ago
> Too bad no good examples for C / C++ projects in Circle CI 2.0. Barrier to entry too high compared to Travis CI. Hahaha, just stop using C/C++. It's 2017 for god sake why do you want to write inefficient, memory-unsafe,
7.
▲
by
heja_bruh
9y ago
They got some time to re-implement javascript parts into another shitty memory-unsafe language, and it's trending on HN. What a time to live-in
8.
▲
by
heja_bruh
9y ago
When are we getting official support for superior languages without GC? Say like Rust?
9.
▲
by
heja_bruh
9y ago
Another reason why we should not be using c++...
10.
▲
by
heja_bruh
9y ago
This is why I've lost respect for lots of developers. I mean why the heck would someone re-implement a piece of code in memory unsafe language? We've a better language now, but this habit isn't dying very soon...