Viktor Hubert

If you ever thought to yourself: "I wish I could support the maintainer of use-resize-observer", well, now you can 🙏: github.com/ZeeCoder/use-r… #oss #funding #OpenSource

@The_Davos_Man yes

I met Hungarians who told me the only reason they voted for Peter Magyar is so he would make it possible for them to vote for someone else in a fair election in 4 years.

@darthcap1tal @GergelyOrosz many left - and are still leaving - because of the current government. I've lost count of the number of people saying they'd return of there's meaningful change. (some even after 10 years)

@GergelyOrosz Citizens living abroad should quite honestly not get a vote. What vested interests do you even have in that case?

Today, Hungary votes. The choice is between an anti-EU, pro-Russia, pro-corruption party reigning for 16 years (Orbán’s party: Fidesz) or a pro-EU, anti-Russia, anti-corruption party (Tisza). My mail-in vote went for Tisza ❤️🤍💚 A rendszerváltásért!

@GergelyOrosz áradjon

Elections are coming up in Hungary, and the campaign is surreal. Orban (the current PM) is effectively saying anyone voting for him votes for Putin and Russia (repeats Russian propaganda, and claims anyone voting for the opposition [Tisza] votes for Ukraine and Zelenskiy (??) )

@Dkr19551970 @BohuslavskaKate it's a gimmick, trying to look smarter. he's basically just doodling. he did this during a Hungarian interview as well, and people made a shirt out of it 😅

@BohuslavskaKate Why is he writing in the middle of an interview?

HOST: "Do you not think that Putin is the aggressor? He chose to cross the border, he's committing war crimes. Is there not a moral duty, to support Ukrainians as the victims in this particular conflict?" Viktor Orbán: "No, I don't think so." An ugly toad proceeds to spew russian propaganda bullshit, which essentially comes down to: Ukrainian children deserve to be bombed in their beds because 'NATO bad'. I'm really looking forward to the Hungarian people voting him out next month.

@theo ouch

If you recognize this image, I hope you enjoy your upcoming retirement

@VolodyaTretyak it's all over the country, in other cities too. anyone I so far talked about these said it's over the line / disgusting

Anyone from Budapest here? How often do you see these actually?

@WillAttract @Kurz_Gesagt is this your voice?

"A loyal Man... will annoy you like a child."

@bryancsk @BohunkSupremacy how naive xd

@BohunkSupremacy ...is the lard heated? Are the bread and onions at least a little bit toasted?

Hungarians be like, “I’m hungry; Imma eat a slice of bread with pig fat and onions.”

@godofprompt their explanation was the same too: the bacteria never stopped "evolving", in the sense that things were reorganising under the hood, eventually allowing for this new ability. basically sounds exactly like "grokking"

@godofprompt only skimmed this but this looks exactly like what happened in the longest running evolution experiment (see on yt on veritasium, 10:40). there e. coli suddenly evolved to consume a second carbon source that was always in its environment: citrate.

🚨 DeepMind discovered that neural networks can train for thousands of epochs without learning anything. Then suddenly, in a single epoch, they generalize perfectly. This phenomenon is called "Grokking". It went from a weird training glitch to a core theory of how models actually learn. Here’s what changed (and why this matters now):

Next.js 16 • Cache Components • Turbopack enabled by default • Turbopack file system caching (beta) • Optimized navigations and prefetching • Improved caching APIs • Build Adapters API (alpha) • React 19.2 nextjs.org/blog/next-16

@DavidKPiano @jrabell0 wow I'm amazed by some of these takes. Good did we get here where the cascade is a con in CASCADING Style Sheets? We've strayed too far from well designed BEM / OOCSS

@jrabell0 You mean how CSS normally works?

But now your browser will have to make a recursive search on DOM tree to apply the styles

@MarcJSchmidt marketing? never heard of deepkit

ok serious talk, why was deepkit not a wild success, and why has it not replaced nestjs yet? what do we need to improve? what is missing?

@dhh so well put

Parenthood gives you a stake in your local surroundings that's load-bearing for maintaining civilization. I don't think it's a coincidence that SF became San Fransicko after decades of VC culture propagandized the family-later-but-grind-first ethos for startups.

@sriniously lovely summary

I study the history of software because most people think code innovation happens in a vacuum. They see React and think Facebook just invented components. They miss the decades of work on MVC patterns, the failed attempts at web components, the slow evolution from server-side rendering to SPAs, the quiet advances in JavaScript engines. When you know history, you see that every breakthrough is built on a mountain of failures and incremental progress. Git exists because Linus got angry at BitKeeper licensing. Docker works because Google needed better process isolation and FreeBSD had jails. React happened because Facebook's ads team kept breaking each other's code. Redux exists because Dan Abramov was frustrated with Flux boilerplate. TypeScript works because Anders Hejlsberg spent years on C# generics first. Node.js exists because Ryan Dahl was tired of Apache's threading model. MongoDB got popular because MySQL couldn't handle JSON well and hardware got cheap. GraphQL happened because Facebook's mobile apps were too slow with REST. Webpack exists because Tobias couldn't get his code splitting to work with existing bundlers. Babel works because the TC39 committee moves too slowly for real applications. Kubernetes exists because Google had Borg internally for a decade. Terraform happened because Mitchell couldn't provision AWS consistently with shell scripts. Electron exists because GitHub wanted to write desktop apps with web tech. VSCode works because Microsoft spent years learning from Visual Studio bloat. Slack got big because IRC was too hard for non-technical teams. Rails happened because DHH was building Basecamp and hated Java frameworks. Django exists because newspaper developers needed something faster than PHP. Laravel works because Taylor Otwell was frustrated with CodeIgniter's limitations. Express.js happened because TJ Holowaychuk wanted something simpler than Sinatra for Node. FastAPI exists because Sebastian couldn't get async to work nicely with Flask. PostgreSQL is good because IBM spent decades on relational theory first. Redis works because Salvatore needed a fast session store for his web app. Elasticsearch happened because Shay Banon couldn't get search working with Lucene easily. SQLite exists because D. Richard Hipp needed an embedded database for warships. RabbitMQ works because telecoms solved message queuing problems in the 80s. AWS happened because Amazon's infrastructure team got tired of manual server provisioning. Heroku exists because Adam Wiggins wanted Rails deployment to be git push. Netlify works because Matt Biilmann couldn't deploy static sites without pain. Vercel happened because Guillermo couldn't get serverless functions to work smoothly. Docker Compose exists because fig got acquired and developers hated YAML complexity. CSS Grid happened because designers were still using tables for layout in 2010. Flexbox exists because float hacks were breaking responsive design. Sass works because CSS couldn't do variables or nesting. PostCSS happened because autoprefixer was just one small utility that worked well. Tailwind exists because Adam got tired of naming CSS classes. This changes how you think about the future. Instead of believing in magic moments of genius, you start to see the slow currents that carry ideas forward. You notice when multiple teams are solving the same problem. You can spot which paradigms are ready to combine in new ways. History also shows you that most predictions are wrong. JavaScript was supposed to be a toy scripting language. Object-oriented programming was for big enterprise systems. The cloud was for startups. Mobile was just a smaller desktop. But the patterns are real. New abstractions always leak. They always find uses nobody expected. They always create new complexity that needs new tools. If you know this, you can navigate change instead of being surprised by it. Most importantly, understanding history keeps you humble. Every generation thinks it invented clean code. Every framework thinks it disrupted everything. But software is a long conversation between the living and the dead. We build on what came before, just like everyone who comes after will build on what we do now.

@mattpocockuk @jetbrains Junie all the way

Who's using async coding agents? Like Jules, Codex, GitHub. How are you getting on?

@isharduld OOP is fine, great even. inheritance can be dodgy. prefer composition and whenever possible instead and it'll be ok

Everyone says OOP is bad, but nobody will tell me why. Is there a secret club I’m not invited to?

@theo @jetbrains + Junie FTW

Which IDE do you use primarily?

@GergelyOrosz I often wonder how non-coders manage. quite often I have to open up the dev tools to fix expected functionality. (esp. for government sites) Sometimes I just need to check the error response from the server that's not communicated through the UI, etc

Tried to reserve 4 seats next to each other for a movie where there were a total of 5 seats remaining free in the row The web app did not allow booking seats to have an empty seat left so was impossible But check was on client-side: so I overrode it Love being a dev sometimes