ivanjermakov

3 ms·

1.
by ivanjermakov 2mo ago
In Russian it's quite common too. Car can be feminine (машина), masculine (авто/автомобиль), and neuter (транспортное средство). And different car brands usually have their own gender too: for example Mercedes is usually masculine
2.
by ivanjermakov 2mo ago
> nobody ever makes grammar errors related to gender For most words, yes. Some loanwords are tricky to gender because of their declension. For example gender of "coffee" in russian is highly disputed: https://www.red
3.
by ivanjermakov 2mo ago
"Having a blog is cool these days"
4.
by ivanjermakov 2mo ago
LSP is not that bad. They tried to decouple IDE features from language features. Resolving file paths is not trivial because it's language specific. Syncing source changes on the LSP server side is necessary to keep packet side small a
5.
by ivanjermakov 2mo ago
I'm not using proprietary git hosting again.
6.
by ivanjermakov 2mo ago
"Industry standard"
7.
by ivanjermakov 2mo ago
> but I haven't seen anything like this before Just a bunch of controversial ideas: structured programming, null, intellisense, microservices, cloud first, serverless, OOP, "Clean Code", exceptions, SaaS.
8.
by ivanjermakov 2mo ago
Same! I decided to reinstall Windows and MBR to GPT conversion (surprisingly!) wiped the whole disk. 10 years of family photos gone. Good thing we had all important ones printed.
9.
by ivanjermakov 2mo ago
WGPU/Vulkan don't work with PTX shaders by default, additional translation would be needed. On a side note, Vulkan has extension to launch CUDA kernels: https://docs.vulkan.org/refpages/latest/refpages&#x
10.
by ivanjermakov 2mo ago
Might be one of the only use cases where LLMs are necessary to succeed. Can't imagine the pain of reverse engineering a technology of this scale and "secrecy".
11.
by ivanjermakov 2mo ago
I see Zig news quite often here. The rest - not so much.
12.
by ivanjermakov 2mo ago
That's my point, diligent use of AI is indistinguishable. And because of bad rep we will see any bad code called out "AI slop".
13.
by ivanjermakov 2mo ago
It's not about who wrote the code, rather who made decisions.
14.
by ivanjermakov 2mo ago
> I'm not sure what to do with the information Get inspired and spend a rest of your life looking for new 3bp solutions.
15.
by ivanjermakov 2mo ago
I solved this by writing a trivial Node http server Telegram bot that accepts messages on root endpoint and sends them as bot messages. 100LOC. Of course the difference is that it's not SaaS and you have to host it somewhere. https:&#
16.
by ivanjermakov 2mo ago
$702 more is relative and tells nothing without the basis. It's 61% increase in 5 years.
17.
by ivanjermakov 2mo ago
Make cool stuff because the process is fun and makes you learn?
18.
by ivanjermakov 2mo ago
Worst part is that it's often not clear at the first glance was it something carefully crafted or steamrolled by LLM.
19.
by ivanjermakov 2mo ago
It's an economical miracle too. Rare case where producing one sellable product is identical in costs to producing millions. And international distributuon and scaling is simple too, compared to physical goods.
20.
by ivanjermakov 2mo ago
To be fair it's a great way to accept donations.
21.
by ivanjermakov 2mo ago
Should be easy to purchase a 2.4GHz jammer, about as easy as to get in trouble for using it though.
22.
by ivanjermakov 2mo ago
Imagine the world where open-source is collaborating instead of fragmenting. Single Linux distribution, single compartibility layer for other OSes, single graphics API, single package manager...
23.
by ivanjermakov 2mo ago
No mention of Tom7's "Badness 0" by the author is the a crime!
24.
by ivanjermakov 2mo ago
Debug allocator can't catch it because it's not an allocation bug. Debug allocator finds bugs by marking memory during alloc/free and inspects them upon deinit. Pointer to a memory location change is not something allocator h
25.
by ivanjermakov 2mo ago
I count this as a "rookie at system programming" mistake alongside returning a reference to a local variable. Rust is great at this because borrow checker can catch those at compile time and it can _teach_ devs to not do that.
26.
by ivanjermakov 2mo ago
Some kind of proof of stake might be viable. "I as a visitor stake 1 cent that I'm a genuine user and not a sloppy bot, server is free to withdraw my stake if it's not true". If works, withdrawn money can be used to cove
27.
by ivanjermakov 2mo ago
There has to be some not-yet-discovered way to have a capcha that is easy for any human but impossible for robot. Too bad capchas hurt user experience no matter how easy they are. Another solution I came up with while reading HN comments: w
28.
by ivanjermakov 2mo ago
Three levels of GUI workflow operation: touchpad < mouse < keyboard. This is the main reason people fall in love with programs like vim: with enough experience it allows one to completely eliminate interface friction.
29.
by ivanjermakov 3mo ago
Nobody complaints that MS laptops ship with Windows - this is about hardware companies partnering with MS.
30.
The Sane Rendering Manifesto(gist.github.com)
2 points by ivanjermakov 3mo ago|0 comments

More ›