Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
bfrog
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
28 ms
·
361.
▲
by
bfrog
3y ago
would love to get like a soft core overview of all these riscv cores. Like are they open source, what sort of coremark score do they get, how big are they, etc neorv, serv, vexrisc, nios v, microblaze v, etc
362.
▲
by
bfrog
3y ago
Because c++ doesn’t already have enough bullshit it needs some more
363.
▲
by
bfrog
3y ago
Depends on how you look at it. How many risc competitors were left after the itanium came out?
364.
▲
by
bfrog
3y ago
C++ makes things very hard to reason about still compared to Rust even. C++ programmers are bike shed machines in my experience, always chasing their own ideal of pedantic C++ which does not exist in practice. How would C++ features like
365.
▲
by
bfrog
3y ago
Rust can prevent races. It cannot guarantee no Deadlocks by itself. However, there are schedulers that do guarantee deadlock free operation written in Rust, see RTIC for example.
366.
▲
by
bfrog
3y ago
Doubtful, C++ tends to bring exactly this sort of persona to the forefront
367.
▲
by
bfrog
3y ago
That goes against the entire premise of C++ developers mindset.
368.
▲
by
bfrog
3y ago
I wish the US would get its act together on stuff like this but it’s too busy getting campaign funds from such schemes
369.
▲
by
bfrog
3y ago
With or without binary blobs and undocumented registers/IPs?
370.
▲
by
bfrog
3y ago
Yeah but it’s still qualcomm, have they managed to open up a bit with their docs/sdks?
371.
▲
by
bfrog
3y ago
It seems like every 5 years I hear about how someone is going to make python not have a GIL, improve performance drastically, etc etc. Then reality comes in and says, "nah". Honestly at some point its better to likely start portin
372.
▲
by
bfrog
3y ago
96 cores? Wild! Can the cores even stay busy and fed with work to do at some point?
373.
▲
by
bfrog
3y ago
Lightweight is a misnomer. Running even the most basic of tasks requires an insanely complex setup with vxlan, unintelligible iptables and bridge rules, all taking up a great deal of resources on something like an embedded x86/arm devi
374.
▲
by
bfrog
3y ago
They work reliably with a lot of unseen work. Debian is a great distro as a user. The .deb packaging tools I found to be a huge hassle and made packaging up missing or updated or custom software a pain in the ass.
375.
▲
by
bfrog
3y ago
Have you built a .deb with debuild and debhelpers? Can you recall all the goofy rules about what needs to go in each file and what each debhelper does? How do you keep all of it in version control and build downstream packages that depend o
376.
▲
by
bfrog
3y ago
This seems like a possible beacon of safety critical rust, especially given that it's SIL 4 and ASIL D (impressive!), the price structure is very reasonable, and its open source! It's really quite amazing what the team there has d
377.
▲
by
bfrog
3y ago
Well certainly part of it is much of the .deb ecosystem still feels like its stuck in the late 90s linux era to me. But maybe I'm alone on that gut feel.
378.
▲
by
bfrog
3y ago
My x220 is endlessly repairable already,what happened was they went the wrong direction in that regard shortly after.
379.
▲
by
bfrog
3y ago
That doesn't sound that beneficial honestly
380.
▲
by
bfrog
3y ago
Lets see I guess... I'm not holding my breath, but it'd be great to not use Vivado's slow ass Java IDE one day. Quartus is light years faster seemingly.
381.
▲
by
bfrog
3y ago
Pretty nice, though feels a bit slow to me... on my 10980xe which is kind of painful I guess given that it's mimicing a late 80s/early 90s video poker machine
382.
▲
by
bfrog
3y ago
"a customizable fpga into our CPUs" that already happened, it just didn't happen in x86 land. There have been a good number of products from various vendors that connect up hard cores and fpga fabric. power pc cores, riscv co
383.
▲
by
bfrog
3y ago
MISRA is at best a glorified style guide and short for misra-ble. I have yet to actually see MISRA do much to prevent bugs. I haven't used SPARK and Ada to be frank, so perhaps they are even superior in their ability to catch bugs with
384.
▲
by
bfrog
3y ago
I mean the best static analyzer is rustc bar none, but then you have to drop the ancient dialect known as C
385.
▲
by
bfrog
3y ago
Right, people have created whole new languages to solve those
386.
▲
by
bfrog
3y ago
Affordable living can be had, where only the citizens can buy land. E.g. the philippines has quite affordable housing. And magically only filipinos can buy land. Coincidence?
387.
▲
by
bfrog
3y ago
One aspect of the Philippines that amazed me was that you need to be Filipino to own land. Why this concept is so difficult to realize in the USA is baffling.
388.
▲
by
bfrog
3y ago
I mean I really have a hard time going backwards on the whole idea of lifetimes and send/sync type traits which force escape hatches if you want to do something idiotic. The key piece here is, any project of significant size and usage,
389.
▲
by
bfrog
3y ago
In effect this answers my question pretty well, the answer seems to be a resounding "No there's no memory safety" at least in the practical or realistic sense that results in few to no memory lifetime errors.
390.
▲
by
bfrog
3y ago
To me the biggest win in Rust is just that, the memory related bugs are nearly non-existent. Throw in a group of people working on something and this makes the project move just so much faster in both review time and time hunting bugs.
More ›