severien @ severien @lemmy.world

Posts

0

Comments

307

Joined

2 yr. ago

If no, they aren’t the problem and shouldn’t feel it’s directed to them.

"boomers" is a name of a generation, not of political affiliation or attitude to youngsters. People don't choose their year of birth.

It's not much different from e.g. gender or racial stereotyping and what you're saying is pretty similar to "if you're not lazy, don't feel offended, you can think of yourself as honorary white".

boomers have been blaming us millennials

Which boomers? All of them? I don't think so...

They grew up with the countries best safety net and support and then proceeded to pull up the ladder after them.

Well, my parents didn't have any such benefits (and generally had much harder life than my generation), and didn't pull any ladder, yet they are "guilty" by the virtue of being born in the wrong years.

Doesn't seem right to me.

And it’s only when they complain about younger people when it really comes up.

Nah, it comes up all the time on social media on its own.

Not sure what your point is, there wasn't much trade between US and the West until about 80s. Soviets certainly could end all trade with evil capitalists, if they wanted.

Countries like Iran or North Korea even have the luxury of capitalists themselves decoupling from them.

Of course it's necessary to be antagonistic towards breaking international agreements.

There's a couple of countries without capitalism, you could try to live your dream there.

• generation hate, ageism, collective guilt - it's getting normal to blame a whole generation (typically boomers) for all the wrong things in this world.
• websites requiring login to see content which isn't anything privacy related - twitter, quora, instagram ...
• services which require a smartphone app and don't provide a website version.
• it's been more than ten years now, but the fragmentation among messaging services. I mean, before that, everybody used ICQ which was a proprietary platform as well, but you had all these different clients and the platform was therefore quite open. Not anymore. I dislike RCS as a possible solution, because it's carrier based and tied to your phone number.

Fahrenheit is no better than Celsius to plan your day, but it's very useful to have just one scale to do both science and your day planning (and everything in between).

Why would you not want to be using a rendering library?

Because it's just not very useful in some contexts. I've seen web extensions which mostly query the current page, and it doesn't render much or even anything.

Not all pages are SPAs either. Many apps are the old request-response with some dynamic behavior sprinkled on top. jQuery covers that well.

This model is also quite compatible with the rising HTMX where the state/rendering is driven from backend and you just insert few dynamic pieces with JS.

document.querySelector("#element").classList.toggle("hidden")

There's no difference between document.querySelector("#element") and document.getElementById("element"), they're both same level clunky.

Also, what you wrote is not functionally identical. $el.show() is idempotent, the el.toggle("hidden") is not (as the name suggests, it toggles a class). It also needs an extra boilerplate class.

I could see not wanting to use a rendering library if you’re building a simple site on top of basic static HTML, but that’s not a serious discussion for industry professionals

There are plenty of non-professionals doing web stuff and I think it's great!

jQuery is such a heavy dependency for saving some characters

jQuery is 24 KiBs (minified, gzipped), that's a good price for the egonomics it provides. If you're constrained, there are API-compatible alternatives like cash which go down to 6KiBs.

There are multiple ways to hide an element yet they standardized on one that often wouldn’t work.

It's the most common one. And it's not like you can't hide the element with some other mechanism with jQuery.

Also you’re using an ancient method getElementById…

And? What's the difference from document.querySelector() when querying for ID?

So what is the right way to do that in modern js?

What is the right way is context dependent. I don't see how having extra .hidden { display: none; } boilerplate is somehow modern or superior.

What was his ethnicity then?

It's kinda interesting how soon Vietnam started to warm up to US, the process started already in the 80s.

Python is for some reason darling of many, sometimes it has almost religious connotations. Meanwhile differences from e.g. PHP are mostly superficial and each has their strengths and weaknesses.

Bourne shell is orders of magnitude worse clusterf*ck than JavaScript, yet it's rarely criticized.

Rust rarely gets criticized which isn't necessarily a problem, since it's IMHO a good language for its intended use case. But people tend to recommend it for things where the trade offs come out negative. (apps not needing max. performance)

In general I wouldn't follow the trends on social media, it's all a huge groupthink, mostly focusing on (easily avoidable) warts, and ignoring strengths.

You know which one. Austrians were considered (and most identified) as Germans before WW2. Insisting they weren't of German ethnicity is a historical revisionism.

Yes, the features are there. Just the API is still horrible.

As an example, make a hidden element visible (extremely common imperative operation).

jQuery:

 javascript

    
$("#element").show();

  

Native JavaScript:

 javascript

    
document.getElementById("element").style.display = '';

  

I hope you'd agree that the native JS is certainly not an example of good API.

Musk provided terminals and connections initially for free, a contract with US for compensation was awarded only later.

The policy to provide coverage only in Ukraine controlled area was there all along, so that was clearly part of that contract.

Again, I very much dislike Musk, but then I also dislike when hate obscures facts.

It's still the best API for imperative access to DOM.

Unpopular opinion: I hope it's going to be a flop (apart from the few use cases where it does make sense). The limitation of having just JavaScript ensures level of interoperability which is IMHO one of the big advantages of web as an application platform. If WASM becomes successful, it will fragment the web.

That's not true, deno compiles TypeScript to JavaScript, it just does it transparently. The code still runs on v8.

That's just twisting of reality.

I hate Musk, but Starlink has been immensely important to Ukraine, I remember Michael Kofman saying that if there's one wonder weapon in this war, it's the Starlink.

What Musk did was refusing to help more. Shitty move, but it's absurd to call it "helping Russia". You also aren't helping Russia because you don't send all your discretionary income to Ukrainian army.