egeozcan

> It poisonous to say elections are “rigged” unless you can prove votes were manipulated

The votes were grossly manipulated through undisclosed funding. This would cancel the results in any democratic country.

Yes, you need stupid amounts of money to win, and I see that as normal in capitalist countries given how significant winning is. However, there's also an obligation to disclose the funding sources so people can decide whether they agree with them.

Some may downplay the importance of this, but I see it as absolutely crucial.

> he who gets the most votes wins, even if the powers that be don’t approve

Through fair elections, yes. No election is ever 100% flawless as perfection isn't practical. However, what happened here is blatant cheating involving shady funds.

> There is a lot of middle ground between "brushing it off" and cancelling a whole election and throwing the choice of millions of voters to the trash.

If elections are rigged, the results cannot be accepted under any circumstances. Using shady, undeclared capital in elections amounts to cheating and invites outside influence. This is a serious issue because we entrust the governance of nations to those elected by the people.

Democracy only functions if the outcomes cannot be bought. While no system is ever 100% immune to corruption, blatant disregard for election laws cannot be taken lightly.

If irregularities occur, people can vote again. Yes, redoing elections costs time and money, but if voters still choose the same leaders after understanding how they gained power, then that's democracy in action.

For me, the line is very clear because I've seen it blurred so many times in Turkey, where I come from, and I’ve witnessed the devastating consequences.

Life in the EU is amazing for me, and probably for you too, as well as many others enjoying it here. However, we can't overlook the struggles of those who are turning to radical populist parties.

They can encode AV1 even. Really amazing, amazing chips for the price.

The "stupid" thing with them (maybe) is that they cannot do anything exceptionally good, and that while having compatibility problems. They are cheap yes, but there are many other chips for the same price, and while they are less capable, they are more compatible.

Make A380 cost 30% less or invest way more to the drivers and IMHO it'd been completely different.

Only time can tell.

Those scripts work, until they don't and the people who generated them cannot even ask the right questions to an LLM, and people who can actually maintain them get overwhelmed by the side-quests of keeping them in order, because everything that gets some use become a dependency for the business.

Some people do not care about safety so we should change the definition of what a recall is and blame an article for being deceptive?

You gave a bunch of examples of some people not caring about safety then generalized to everyone. You may be in a bubble, or you may not be, but you're presenting zero evidence to call the article deceptive.

On https://www.nhtsa.gov/recalls#recalls-7746 it says:

> A recall is issued when a manufacturer or NHTSA determines that a vehicle, equipment, car seat, or tire creates an unreasonable safety risk or fails to meet minimum safety standards. Most decisions to conduct a recall and remedy a safety defect are made voluntarily by manufacturers prior to any involvement by NHTSA.

> Manufacturers are required to fix the problem by repairing it, replacing it, offering a refund, or in rare cases repurchasing the vehicle.

So the person you're replying to seems to be correct, or is there another source that shares your claim that "the focus is, and always has been, on the physically give your car back to manufacturer part"?

Nearly 30 years ago, as a kid with way too much free time and a budding interest in questionable DIY projects, I decided to stroll into a hardware store and try to buy some very suspicious items I'd read about in an online forum.

The saleswoman, bless her soul, looked genuinely concerned as she told me she couldn't sell me what I asked for. Then came the inevitable: "So... what exactly are you planning to do with this stuff?"

Without missing a beat, I launched into an impassioned explanation about how absolutely epic it would be to blow up this colossal ant nest I'd discovered in our neighborhood.

What followed wasn't the cool supplies or cheers I imagined but a long-winded lecture about how ants are living beings too, and how it's "definitely not okay" to blow them up. No cops. No parental intervention. Honestly, that lady could've reported me to my parents or even the authorities, but nope! This was Istanbul, and I happened to be a "local" (Funny because there are no locals in Istanbul) kid with lighter skin and blue eyes. So, all good!

But as I got older, I realized how lucky I was. If I'd been darker-skinned or Kurdish (which, back then, was basically a surefire way to get labeled a "terrorist" in the media), things could've gone very differently. Today, it's Syrians who face the brunt of the suspicion. Tomorrow? Who knows!

What I've come to understand is that this kind of dumb, knee-jerk profiling based on race and appearance is everywhere. Humans are exceptionally good at spotting patterns (real or imaginary) and we'll keep doing it as long as we're fed bad (or any, really) information. Even now, living as a migrant in Europe, I get my fair share of this nonsense. Some things, unfortunately, never change.

The serenity I had while sitting in a train is the only thing I seek from my office days. I actually listened to audio books and learned, or just watched outside and thought about nothing.

Catching cold every 2 to 6 weeks on winter wasn't amazing though.

> Why can't I await in a normal function? await sounds blocking

> You can await in a normal function in better languages, just not in JavaScript.

Await, per common definition, makes you wait asynchronously for a Task/Promise. How on earth are you going to "await" for a Promise which also runs on the same thread on a synchronous function? That function needs to be psuedo-async as in "return myPromise.then(() => { /* all fn code here */ }), or you need to use threads, which brings us to the second point...

With the closest thing to threads (workers) in JavaScript and using SharedArrayBuffer and a simple while loop, perhaps (didn't think too much on it), you can implement the same thing with a user defined Promise alternative but then why would you want to block the main thread which usually has GUI/Web-Server code?

I really don’t like the term "bus factor" because I lost someone in a bus accident.

On the other hand, millions of lives have literally been lost on various hills on various battlefields, yet no one seems to mind when someone says, "this is the hill I’m willing to die on." :)

Luckily I have a real life example from a customer project I was involved as a consultant: Integrating a custom identity provider with multi-factor authentication. This was from many years ago though. They also used to have some performance problems in some naively implemented middleware and needed to deep-dive into how things actually work before being able to optimize. And commands - I was doing the integration with our software and their command queue was always causing problems with stuck jobs until they read the implementation. The specific problem with Laravel as a product is (was?) that the docs are too beginner oriented and perhaps "you don't need to know what's under the hood" mindset is exactly what's causing this. I got to know many experienced PHP developers who got really frustrated because of the ELI5 style docs.

You can't always rely on the docs too, however excellent they may be - some game developers read code from game engines to optimize, some web developers read code from their web frameworks. But, some change their whole stack when they get frustrated, and I argue that it makes little to no business sense to do so. Just understand what you are working with and deeply.

My impression after many years of working with JSF: PrimeFaces or not, it's a lot of server-side state making it hard to work on the front-end and an unnecessary burden on the server.

I have also some nice things to say, and I'm not going to make a detailed analysis here but IMHO, it's really not worth the tradeoff.

I did write a lot of Java but never called myself a Java developer, and in my current company there are a lot of hardcore Java devs who used to swear by the Spring stack (some even liked JSF!), and a lot of them are moving things to Quarkus (https://quarkus.io/). No idea why, just an observation.

From my experience, these frameworks are like the express lane for kicking off a project because there are no big decisions to make. But once you’re knee-deep in Rails, Django, or Laravel and need to do something off the beaten path, things can get dicey. Why? Because you didn’t write the glue code yourself, so there's a gap in understanding, not really a technical roadblock (most of the time!). My point is, if you dive into these frameworks and actually learn the guts, you'll save yourself tons of time coding by, well, reading code.

Now, do I actually do this? Absolutely not. Rewriting everything is way too much fun, and I live for the thrill of trying new things, even if it makes zero business sense.

> Using SQL queries is typesafe with Kysely https://kysely.dev/ (without the need for an ORM)

Wow, this is even better than what I've seen people do with F# type providers. Cool cool cool.

I recently implemented this, and the users loved it, though I was disappointed to hear it may have frustrated a usually silent group.

I'm open to feedback! What would be a better approach? Please don’t just suggest “no custom shortcuts for any web app”—people spend 60-70% of their workday using the UI components my team maintains. While random sites hijacking shortcuts is definitely frustrating, in our case, the pros seem to outweigh the cons.

Maybe allowing users to disable or customize shortcuts could be a solution? Or would that be over-engineering?

Honestly, I think the web platform could use a standard API for defining shortcuts, with browsers providing a UI to manage or disable them. Maybe I'm still over-engineering here.

Would really appreciate hearing others’ thoughts!

Actually most use the HTML video element but use JS to download blobs and add them as src, and/or bury the elements like this:

https://imgur.com/C8AP7y0 (random video I found on threads as an example)

Just to break native download functionality and/or add own silly controls on top.

Declaring a stdlib free of rough edges would be like declaring a complex piece of software bug-free.

It would solve many of my complaints as well.

But, to be honest to myself, I don't think anything will be too different in my day-to-day programming, nor that I would produce better code with less bugs.

Oh it gets weirder in Germany! See: https://en.wikipedia.org/wiki/Beitragsservice_von_ARD,_ZDF_u...

The tv license collection agency employs more than a 1000 people.

And this is in spite of the fact that nearly every household has to pay that €18.36 per month.

President of Turkiye? Many years ago, a person I know got arrested for calling that guy "clueless" on Twitter under a nickname.

Disclaimer: Erdogan is the ultimate ruler, he's totally the best. That guy I know totally deserved it!!11

ps. I like my vacations in south Turkey.

It will be. Any time you offer something that allows anonymous uploads & shares (hell, sometimes even if you don't allow share, people will share accounts), it will be a silo 95% full of material that's illegal in practically every corner of the world.

If you play the good citizen and encrypt the files, giving the key to the owners, then you also don't have any means to preemptively detect and delete that stuff, you just keep waiting on some law agency knocking at your door. Also, if you openly say "hey I'll peek into your files to see if they are legal", then they will be the ones encrypting. Disallow that? It's a nightmare to detect and abusers are really, really creative! So much dedication too!

And it's not just CSAM, there will be detailed instructions on practically any illegal thing you couldn't even imagine.

It's bad, really bad, and I've grown to accept that small, closed community services (best with real-world connections) are the only way forward.

Thank you! Great idea, I'll give it a try :)

I would be very thankful if somebody actually did this!

Also make it dynamic so every time screensaver activates CPU gets hot, heating the room, removing the need for me to keep pressing the space bar.

I copy the images in my clipboard and save them in an HTML file to have single-file galleries:

https://gist.github.com/egeozcan/b27e11a7e776972d18603222fa5...

Live:

https://gistpreview.github.io/?b27e11a7e776972d18603222fa523...

Selecting via file-picker works too. Dragging usually does not. When all works, images are inserted inline as blobs.

After adding images, if you save the page (literally file->save), the blobs are saved together. don't want a part when saving (for example, removing images)? inspect element, remove, save page.

throw the page on some server or just double click on your computer/mobile.

> ...how it (the Wordpress community) has been made to depend on Matt’s leadership at Automattic’s infrastructure. And how that is a very bad thing.

> This post is best read while listening to Know Your Enemy by Rage Against the Machine. (There’s a jazzy cover if you are so inclined.)

Well, I hope nobody needs to listen to "(This is what you asked for,) Heavy Is the Crown" when listening to the future developments :)

I'm not on team WP Engine or Matt, and I have no personal stake in this (I don't use WordPress). But at this point, I’m concerned that things are going to crash and burn, impacting the average blogger who just wants to publish content - far more than they’d ever expect. I dislike Medium even more than I dislike the WordPress ecosystem.