Readit News logoReadit News
neysofu commented on Google Antigravity   antigravity.google/... · Posted by u/Fysi
badenglish · a month ago
Once upon a time, all you needed to program was a compiler. Now, it's moving toward paying to write code. This will certainly kill open source
neysofu · a month ago
All of this is entirely optional. You're free to code the "old-fashiond" way, if you so prefer.
neysofu commented on Why Tap a Wheel of Cheese?   cheeseprofessor.com/blog/... · Posted by u/speckx
stouset · 8 months ago
It’s also worth considering that at most you’d be automating 24 jobs.
neysofu · 8 months ago
Indeed. I'd imagine most of the value of such automation would come from supposedly better quality control, not from saving money on salaries.
neysofu commented on Why Tap a Wheel of Cheese?   cheeseprofessor.com/blog/... · Posted by u/speckx
louthy · 8 months ago
If the price of cheese was the only factor then I’m sure practices would have changed. But people will pay a premium for what they perceive as a premium product, so practices like this just add to the ‘experience’.

The watch on my arm is (mostly) handmade and worth a fortune, there are plenty of other cheaper watches that are arguably better due to them being made by robots.

Same principle, I think.

neysofu · 8 months ago
> there are plenty of other watches that are arguably better due to them being made by robots

In the world of watches, this logic extends far beyond "handmade vs made by robots". Quartz, for example, is better than automatic & mechanical in every single quantitative metric, yet perceived as lower value due to the lack of craftsmanship.

neysofu commented on Rust for Filesystems   lwn.net/Articles/978738/... · Posted by u/drakerossman
sanxiyn · a year ago
Note that unsafe blocks don't have limited blast radius. Blast that can be caused by a single incorrect unsafe block is unlimited, at least in theory. (In practice there could be correlation of amount of incorrectness to effect, but same also could be said about C undefined behavior.)

Unsafe blocks limit amount you need to get correct, but you need to get all of them correct. It is not a blast limiter.

neysofu · a year ago
I believe this is technically true, but somewhat myopic when it comes to how maintainers approach unsafe blocks in Rust.

UBs have unlimited blast radius by definition, and you'll need to write correct code in all your unsafe blocks to ensure your application is 100% memory-safe. There's no debate around that. From this perspective, there's no difference between a C application and a Rust one which contains a single, incorrect unsafe block.

The appreciable difference between the two, however, is how much more debuggable and auditable an unsafe block is. There's usually not that many of them, and they're easily greppable. Those (hopefully) very few lines of code in your entire application benefit from a level of attention and scrutiny that teams can hardly afford for entire C codebases.

EDIT: hardy -> hardly (typo)

neysofu commented on After AI beat them, professional Go players got better and more creative   henrikkarlsson.xyz/p/go... · Posted by u/iNic
acchow · 2 years ago
> Instead of checkmating the goal becomes to capture the opponent's king.

These are the same.

neysofu · 2 years ago
They are not – if the goal becomes to capture the king, and check-related rules are removed from the game, stalemates become impossible.
neysofu commented on After AI beat them, professional Go players got better and more creative   henrikkarlsson.xyz/p/go... · Posted by u/iNic
btilly · 2 years ago
And what happens if you wind up with king and rook vs king and rook?

Some positions simply do not allow for a win. Yes, you could say do it on time. But then it becomes about mechanical dexterity as people try to be faster than their opponent in a pointless piece shuffle.

neysofu · 2 years ago
Yeah, I didn't think it through. I'd imagine such a rule change would still make draws significantly less likely though, right?
neysofu commented on After AI beat them, professional Go players got better and more creative   henrikkarlsson.xyz/p/go... · Posted by u/iNic
Taek · 2 years ago
I think you would see fewer ties if players got 0.2 points each for draws instead of 0.5 points each for draws.

It makes the risk of going for a risky strategy lower (you only drop 0.2 pts instead of 0.5 vs getting an easy draw) and it makes the rewards much greater... a single win and 4 losses scores the same as 5 draws.

you wont see players doing intentional draws anymore either

neysofu · 2 years ago
Another possible solution would be to simply... remove draws from the game. Instead of checkmating the goal becomes to capture the opponent's king.

Needless to say, no one likes this idea because it throws out of the window centuries of game theory. Endgames would be completely different. I'm not convinced it would be a less interesting game, though.

Deleted Comment

neysofu commented on Good times create weak men (2019)   tonsky.me/blog/good-times... · Posted by u/InsiderTesla
Obscurity4340 · 2 years ago
I just wish everybody and all the shareholders could freaking understand this. Cut the infinite exponential growth bullshit, they should be expected to slowly and carefull craft quality products and systems and release like a new generation whatever like no sooner than like 3-4 years. I hate this new year, new phone/laptop/whatver crap.

Its wasteful and sloppy ultimately and makes it hard to be familiar with their actual range of products in tangible way

neysofu · 2 years ago
I'm pretty sure Apple shareholders are doing just fine.

u/neysofu

KarmaCake day240November 7, 2018
About
https://neysofu.me https://www.linkedin.com/in/neysofu/
View Original