See also from earlier today [1].
More or less the same content but parent is much more palpable, IMHO.
3,320 karma · joined June 18, 2010
alias: virtualritz at protonmail
meet.hn/city/52.5173885,13.3951309/Berlin
Socials: - github.com/virtualritz - linkedin.com/in/moritzmoeller
---
More or less the same content but parent is much more palpable, IMHO.
And so I think the idea is more to understand tomorrow ... from first principles.
In the late 80's, as a teenager, I learned x86 assembly and C because that was the only way to squeeze out enough juice from my shitty CGA (and later VGA) card to programm the games/graphics that interested me.
I haven't written assembly in years.
But whatever I did in my career: it helped me and gave me an edge over my peers to have a foundation that is very close to the metal.
And yeah, I helped a friend who's a furniture designer [1] for a few years.
After a while, when you 'beta test' pieces in development a lot, you understand that looks are great but comfort always wins.
That's a pile of bollocks, pardon my French. Source/proof?
And to the contrary:
I've been working on a TS codebase that calls into C++ native/wasm-compiled code for six months now. The code is mostly LLM written.
Over these last six months we had four use-after-free and two other ownership-related bugs in LLM-generated TS code.
Whereas we had zero issues of any such kind with LLM-generated Rust code that sits in another two native/wasm-compiled metacrates we use.
LLMs are not much better at ownership tracking than humans.
Especially if resource acquisition and release are far apart in code and/or somehow nested/stacked/non-straightforward.
I wouldn't find this post less ridicule-inciting than if the title was
"macOS's built-in weather app wastes more that 200 MB of RAM"
Basically it steps through a folder with images, finds corners, user presses Space if ok, or adjusts corner if not (about 1 in 20 pages has a corner wrong). Undistort, contrast correct based on histogram, etc. happens automatically.
On the last page pressing Space creates a PDF.
My brother and I were digitizing medical bills for our mother and everything we tried to do this with out there was meh, cost money or both! It seems as soon as you need PDF anything it's $$$.
This is a throwaway tool as we're now more and more getting bills as digital files anyway.
My only input was specs, otherwise it's "vibe coded" if you want.
But consider that the Rust crate ecosystem is mature and my prof. background is computer graphics.
Oh, and I have an image manipulation crate that I wrote for work (closed source for now, unfortunately) that has corner pin with area filtering as a primitive.
I was just surprised how possible this is now.
This was earlier this year (Opus 4.8 was just out) and while we were photographing the pages with our smartphones Claude wrote the tool.
That is a big lever language designers can use if they painted themselves into a corner.
The dogs bark, but the caravan moves on.
In Europe for sure and possibly many parts of Asia like Japan or bigger metropolises in China etc. most people will commute by public transport.
You can read. Whenever I had a job where I commuted at least an hour a day, the number of books I read, per month, went from 2–3 to 10 or more.
Since hacking on a 3D DCC in your spare time may be more than three times as enticing to people than doing the same on an email client?
I'd wager Occam's razor favors this explanation.
Yes, just like early cars allowed mediocre horse riders to get from A to B with dignity.
Or like my Japanese rice cooker allows a person like me, utterly shitty at preparing this, to eat some rice that is cooked to perfection.
Etc.
Since we do not know the ratio to undiscovered this "1-2" is meaningless to assess the risk of this sort of attack.
Cast into TOS and code. Openly so.
People who grew up on the artificial flavor prefer it over the real one. I have quite a few in my circle of friends.
You go to an Italian restaurant and you get plain pasta, panned in butter or olive oil and then someone comes with a real truffle and grates it in front you of over your dish until you tell them to stop. You pay for that amount.
Unless you go to a restaurant with a great reputation or some Michelin star venue, that is the only way to be sure you're eating real truffles. The dish has no truffle-aroma itself and the truffle is grated while you watch.
Assuming ofc (and probably true for most people): your palate is not well acquainted to the taste of the real thing enough to tell it apart from the many fakes/substitutes.
[1] https://www.tasteatlas.com/truffle-industry-is-a-big-scam
And when you go from float to 8bit you should dither to avoid banding.
If in doubt, error diffusion with a random number between -0.5..=0.5 is fine. 0.5 here is dither_amplitude:
round(255 * input_value + dither_amplitude * random(-1, 1))
See e.g. my dithereens crate: https://crates.io/crates/dithereens
Which happens right after the Porter-Duff Over operator above -- a smoking gun. Which one is it gonna be?
I.e. the display transform is omitted from this and the math involved with the latter makes your whole argument moot.
It can't be expressed well enough with bitshifts to keep your purported 10x speedup anyway (and which I strongly doubt btw).
And lastly: in a software renderer that stuff is usually <0.01% of the compute in the absolut worst case.
P.S.: I'm speaking from 30 years of experience with software rendering in the context of VFX.
Even if one may argue that scripting languages usually abstract ideas like stack and heap away. :)
Same with 'List' vs 'Vec'.
And why are List, String & co uppercase?
From what I gather these are built-in types the compiler knows?
'i32', not 'I32' but 'List' not 'list'? In Rust the case is clear cut: built-ins that the compiler 'knows' are lowercase, types expressed in Rust itself are PascalCase.
Roto seems to mix this?
Reads like Rust but then "differs subtley" where it (seemingly?) does not matter at all.
What is the rationale? I'm not complaining, Roto looks great. I'm considering swapping my Koto integration in my project out for this. :)
I'm just genuinely curious. From the outside the above smell like "just because" decisions.
I would add this as a setting.
In the article, if you were to mention & follow them GetUser() in Go becomes user() in Rust[1], not get_user().
[1] https://rust-lang.github.io/api-guidelines/naming.html#gette...
sRGB or ACEScg are color spaces.
CMYK or RGB etc. are color models.
This matters a lot. And yeah, it seems this supports neither and it is unclear if operations happen in linear light at a bit depth of at more that 8bit/channel.
If they don't, most of them will produce subtly wrong results.
Two types of spaghetti (regular No. 5 and gluten-free) produced by the Barilla company (Italy) were purchased in a supermarket."
Are you kidding me? You did a study and tested /one/ kind of gluten-free pasta?
There are so many different kinds from different companies. One type from Barilla is nowhere near representative to draw a useful conclusion.
Especially as unlike many other gluten-free pasta products it lacks an important binding agent.[1]
As someone with a gluten-allergic partner I regularly make pancakes and bake bread with (Italian!) rice-based flour.
And they are difficult to distinguish from the flour based ones, in taste, texture, fluffiness and and structural integrity.
The secret to this is xantham gum. It acts as a binding agent in gluten-free baking, providing the elasticity and stickiness that gluten typically offers. It helps to hold ingredients together and improve the texture.
I learned this when eating excellent gluten-free pinza, in a small place in Catania, Sicily, whose owner has celiac disease.
Ah yes, as far as pasta goes there is also research about this ofc[2]
[1] https://www.barilla.com/en-us/products/pasta/gluten-free/glu...
[2] "Incorporation of xanthan gum to gluten-free pasta with cassava starch. Physical, textural and sensory attributes"
https://www.sciencedirect.com/science/article/abs/pii/S00236...
People simply didn't /know/ about them/that they existed at all.
I went to a computer/electronics shop in town and asked for them.
The guy told me: "We don't stock them because people don't ask for them."
After switching to Rust five years ago I agree with all the Rust hipsters as far as disliking those languages go.
I just don't talk about it a lot. If every Rust person I know that was a C/C++ developer before was as outspoken about what they think of the latter, you'd see that these people are a majority.
We're just old hands who like to use stuff that works. And most of us don't get attached to code or languages.
It's also difficult to admint to yourself that you were never in command of a language as far as UB/other footguns go, as much as you thought. Or ever, for your enire career. For me that self-realization about C/C++ (enabled by Rust) was a turning point.
Lately you can read about the dichotomy re. AI use.
I.e. developers who define them themselves through what they build/ideas are embracing LLMs; for what they can do.
I.e.: I am what I build.
Whereas developers for whom software engineering is a craft that defines them hate them openly.
I.e.: I am how I build.
Now this seems to suggest to me that maybe Rust developers who openly hate C/C++ squarely belong to the latter group whereas the silent ones belong to the former. It's builders vs programmers. Just different world views.
Also you can not dislike something and still not speak about it. Because you decided to not care.
That is the most important feature this would make me use this over the good old wooden puppet, which is small (10cm). I.e. it travels with me with my drawing utensils.
I guess I am asking: what exactly is the value proposition?
But I don't know enough that's why I asked.
I imagine one could do CTF in public, machines you work on vetted/prepared to some spec, yada yada.
If chess and Go can do it why can't CTF?
That was my question when I wrote "what am I missing here".
What am I missing here?