azangru

> Call me a radical but I’ve chosen not to kowtow to billionaires.

I wonder when the author will be switching from his Mac.

If the argument, which seems to be "code is cheap; let's write implementations for multiple platforms", remains true, what do you think will continue turning the wheel?

Signal requires a mobile phone for an account; so it's not entirely web-friendly. Plus, can you read what's posted to signal without an account?

Well, DHH managed to attract Dell, which are kinda sorta promising through a single representative that their new XPS laptops are fully tested with Omarchy:

https://www.youtube.com/live/Bic2KjFFj6w?si=g0wyGBQi63NmhWr5...

So that's encouraging. But still, I don't see any acknowledgement on the Dell site (apart from a single blog post) about their stance on supporting and testing linux on their laptops.

> given that developers are the one group of people today that don't generally have a problem running Linux on the desktop.

I am a developer; and I do have a problem: I don't have a choice of good laptops that are guaranteed to work with linux, and preferably come with linux preinstalled. I can go buy a macbook, or a windows laptop; but I can't walk into a store and buy a linux laptop.

I hate it when a comment tells me to see JIRA-1234. What if in a year's time we stop using Jira?

All that time spent programming those visuals. Which, I think, ironically, have made the article harder to read, not easier.

Do your sass customers know what javascript is or how it's different from java? Does this mean developers shouldn't care either?

> it's that small businesses cannot buy phones, install a patched version of Android without a restriction

Pardon my ignorance; but why would Android need to be patched? Is it because it wouldn't run on the phone hardware otherwise?

> This new trend of content appearing while scrolling down is so terrible accessibility-wise, I do not understand how Mozilla of all institutions would do it.

Could you explain what is wrong with the accessibility of this page? All the content is included in the html payload, so it is accessible to screen readers and text-based browsers; and as for the "reveal" effect, it seems to respect user's choice of "prefers reduced motion" and is disabled when that is user's preference.

From the title of a chart:

> The venture-funded open-source ecosystem: total disclosed funding, USD M

> Bars grow as you scroll.

The bars, in fact, don't grow as you scroll. And I don't even see why they should.

Not OP; but I would define it as a cluster of specific and strongly held opinions on several topics, such as race/ethnicity, sex, migration, climate change. These opinions cluster together, and produce certain recognizable behaviors including speech patterns, speech taboos, and aggressiveness towards people who do not share these opinions.

I'd rather have something I can tinker with on my own machine, thank you very much

> And then please, please test for prompting with challenging assignments that would usually be beyond a student's skills

Does this mean you will requre all students to pay for a subscription to an llm provider?

> You can cheat on your homework all you like, but you'll completely fail the exams

This might sound principled, but we need to recognize that school administrators are incentivised to have as few kids as possible fail their exams; and consequently, so are the teachers. Either exams will change, or the teaching will change.

Well, at least the copy on the site reads like satire. I didn't notice it at first, looking at components; but then I started reading the text.

P.S.: The popover description is brilliant:

> The obtrusive newsletter modal every AI startup deploys. Takes over the entire viewport with a blurred backdrop. By design, neither the Escape key nor backdrop clicks close it; the visitor either submits the form inside or clicks the tiny dismissal link at the bottom. Pair with `timer` to auto-open after the visitor has skimmed a few paragraphs.

Thanks! Found it.

> Source available in Github through NoSuggest website.

Where? I couldn't find any link to the source on the website.

> Submit a feature (our version of a pull request) that looks and behaves exactly the way I want

What happens after the submission? Who reviews the feature? How long? Are there any limits to the size of the diff? Do reviewers push back? How often are features submitted?

Will there be developers at all then? What would they do? What would define their role? What skills/qualifications would they need?

> Users don’t care whether the code was written by AI or by hand

Users don't. Question is, do developers, who are tasked to read, modify, and maintain the code?

> I earn a small fraction of what NYTimes earns. If I'm not desperate, why are they?

He is an individual, and they are a company of about 6,000 people?

> you need to subscribe to changes manually (use effect) to create computations

How do you mean? Since the render function reruns during every update to state/props, derived/computed values can be calculated from the updated state/props during rendering.

> a typical config & plugins stack for (webpack + eslint + prettier) is nearly impossible to reason about.

I think people just don't want to bother. They don't want to read the docs, or maybe watch a video or two (back when webpack was popular, Sean Larkin, webpack evangelist, made a number of popular courses about setting it up). Also, webpack config became easier compared to 2014/2015; I think they got to practically a zero-config by default.

I can understand that people don't want to care; but "impossible to reason about" is not it. It isn't rust, for crying out loud; nor lisp; nor haskell.

But why is push vs pull the definition of reactivity?

I suppose we can say that there are different kinds of reactivity. Signals is one kind. Observables à la rxjs is a different kind (the whole model of programming with rxjs was referred to as "functional reactive programming"). Observables are push-based. Signals, as I heard, are a more complex primitive, which, under the hood, is push-pull.

React's reactivity model may be crap; but this doesn't make it non-existent.

React reacts to changes in state or properties by automatically updating the UI. What's not reactive about that?

> Observables - streams

> Signals - reactivity

The r in rx stands for reactive.

> have you tried working seriously with claude code or gpt codex and which part of it did you not enjoy?

I haven't. But I found myself, to my surprise, not particularly interested in trying; which makes me wonder what motivates other developers if not peer pressure or demands for more productivity. I find coding interesting and fulfilling enough to do it on my own. I do ask LLMs questions from time to time, but for that, even a chatgpt or a gemini in a browser tab is enough.

The best experience I had so far is with code reviews, when the models pointed out my mistakes. But I haven't yet gotten to the point where I would want them to write code for me.

> battling with AI, trying to get it do what I wanted

What I am selfishly curious about is: is it possible to remain a software developer, and ignore AI? To write code the same way we did before 2022? I understand that there are many companies in which managers demand more of workforce — but are there still places where people are satisfied to not rush ahead and do business same way they did three or four years ago?

In other words, is it possible to not battle with AI trying to get it what we want? Were you forced to do this by your employer, or was this entirely self-inflicted?

Asking for a friend.

> now that Google isn’t really Google anymore

I can't say I've noticed any changes about google search on desktop recently. Yes; there is an AI overview widget at the top of the page; but it's been there for at least a year.

Has anything changed about Google search results for you?