Blaming Js/Ts is ridiculous. All those same problems exist in all environments. Js/Ts is the biggest so it gets the most attention but if you think it's different in any other environment you're fooling yourself.
And yet, tons of developers install github apps that ask for full permissions to control all repos and can therefore do to same things to every dev usings those services.
github should be ashamed this possibility even exists and double ashamed that their permission system and UX is so poorly conceived that it leads apps to ask for all the permissions.
IMO, github should spend significant effort so that the default is to present the user with a list of repos they want some github integration to have permissions for and then for each repo, the specific permissions needed. They should be designed that minimal permissions is encouraged.
As it is, the path of least resistance for app devs is "give me root" and for users to say "ok, sure"
Why spend that effort when any code you run on your machine (such as dependency post-install scripts, or the dependencies themselves!) can just run `gh auth token` can grab a token for all the code you push up.
By design, the gh cli wants write access to everything on github you can access.
I personally haven't worked with many of the github apps that you seem to refer to but the few that I've used are only limited to access the specific repositories that I give and within those repositories their access control is scoped as well. I figured this is all stuff that can be controlled on Github's side. Am I mistaken?
All of them. UBlock Origin does not work on V3. There was a Lite version that used V3 but they stopped work on it because it was so limited. It looks like there's been some updates to it recently now.
The size of blacklists has gone from unlimited to a limited size. The blocking ability has been limited. And the worst of all, blocklists have to be bundled in extension updates and not downloaded. While they have increased the limited blocklist size for V3 overtime, I don't know if they ever changed the other limits.
Here is the official FAQ: https://github.com/uBlockOrigin/uBOL-home/wiki/Frequently-as...
For some context, I currently have 393,405 network filters ＋ 385,476 cosmetic filters.
"The current limit imposed by the various implementations is a guaranteed 30K. It is possible for an extension to use more rules, but anything above the global limit will not be enforced. Currently, the global limit in Chromium is 330K static rules."
Good! because people prefer Chrome. People have to go out of their way to install it and they do.
If Safari was better then Safari would stay #1 on iOS. They shouldn't be allowed force this any more than Microsoft was allowed to force IE.
If 3rd party browsers were allowed we'd have had WebGL2 on iOS 4 years earlier. WebGPU 2 years earlier. WebXR several years earlier (Apple is only adding it now and only for Vision Pro), and many other features.
Japan would like have a word with you. Houses in Japan are like cars. The moment you buy it it's now "used" and worth less and it keeps doing down in value.
That's actually not (much) less true in other places. It's just that in eg the US the land is typically a lot more valuable, and people tend to mix up the value of the land (which doesn't really deprecate) and the value of the structure on top.
>> the value of the land (which doesn't really deprecate)
Maybe in urban centers. But go out into the hills and you will find many towns where land prices tanked once the local resource industry moved on. It isn't just 18th century gold rush stuff. There are towns from the 80s that just emptied when the local industry moved on.
And I assume houses in these places aren't exactly holding up well as investments?
EDIT: Oh, I think you were talking about deprecation? Even in the downtrodden areas, land values going down isn't technically deprecation. It's just like a bar of gold sitting in your garage: its market price might fluctuate, but that has nothing to do with deprecation.
I feel like there should be a followup post "Dear Sir, you have reimplemented quaternions" noting how implementing GA and using it only in 3D gets you precisely right back to quaternions-but-with-a-different-name since they're isomorphic when specialized for 3D.
it's a problem. As soon as it became easy to ask for money via Patreon or githib sponsorship, etc... tons of people are going to try to get some for minimal effort. It's just the nature of the beast.
Asking for money isn’t a problem. The problem is this person went out of their way to extract money by harassing people who rightfully use the open source Apache 2 version, switching the marketplace extension to a closed source version with obfuscated code (likely malicious according to MS), and possibly more, all this for doing a quite small amount of work. That’s after already raising $7.6k, apparently.
Making a theme is not minimal effort which is why 99.9999% of everyone uses preexisting themes rather than making their own.
LoC is a red herring. And the fact that thousands of people decided to introduce his LoC as a dependency in their local development environment makes the point.
I'm surprised to see supposed software engineers get this wrong. We tend to dismiss look&feel type things as low effort which is funny because very few of us could make a make a good theme if we tried, yet it's "just" a matter of picking colors.
Maintaining a theme ~a decade after its creation is minimal effort. You can check the commit history yourself and see it's a one line change once in a while among auto dependency bumps thanks to a >10k line package-lock.json, at least half of which is unrelated to core functionality as demonstrated by t3dotgg.
It's also funny to see a "supposed software engineer" shit on other's tools and post veiled personal attacks based on a single Internet comment. If I were you I'd probably insinuate you've never worked on any large code base so don't know LoC definitely correlates with complexity as a rough first signal (not to mention I included a rough analysis of actual code as well), but I shouldn't do that based on a single comment. Anyway I've maintained plenty of open source code bases large and small, popular (>10k stars, yes that's not a very good metric but it's also a useful first signal) or not, so I'm pretty well equipped to evaluate maintenance burden.
Almost all of the work has already been done by other people for other text editors. Porting a theme requires copying files from another project and writing a tiny bit of glue around it. The author of a niche terminal emulator I'm using on small systems was able to add around a hundred themes this way in a short amount of time. Sadly, he wasn't able to raise $7.6k×100 for all that thankless work.
I think effort is irrelevant. Value is what we really look at when deciding what price to pay. It doesn't matter to most people if it took someone a 1000 hours to produce a loaf of bread. They're not going to pay 100x the price of the bread that took 10 hours to produce. Especially, if the products are mostly indistinguishable.
I think the luxury market proves my point. The perceived value of luxury items is much higher as reflected in the price paid. Although, the cost and effort to produce luxury items is roughly the same as a similar non luxury item.
For me, the #1 reason I don't blog more, especially about tech topics, is that they take too long. Maybe you can bang out a useful blog post in 20 minutes. For me it's more like 4 to 8 hours.
I have to make samples. Since I do mostly web tech I want the samples to actually work, no "here's some code, trust me". I also need diagrams. And, I have to proofread since I'm terrible at getting it right in one or even 5 checks. I write once, add samples, write some more, add images, write some more. Every time I write I add errors, so it always takes multiple passes.
Proofreading is one place that AI can actually be a friend rather than a foe. If you give Claude your draft and tell it explicitly to call out misspellings and grammatical errors only, it does a really good job.
"I started the car and went for a drive on the highway. There were many other cats on the road but it was nevertheless agitating."
Given the correct prompt (that avoids changing your literary style altogether), AI can quickly suggest cats -> cars and agitating -> peaceful, since it's much better at contextualizing.
Proofreading is easily done with an editor. I think AI is much more useful for giving critic and advice on how you write your sentences. Setting the tone, refining the main idea, pointing out redundancies are some of the things that I find very useful.
Sometimes, but you have to be careful. IME Claude and (to my surprise) Grok 3 are really good at understanding your style and adapting their suggestions to match. ChatGPT, by contrast, tries to change everything into some kind of corporate drone.
My drafts usually live for days, weeks, or even months before I publish them. (And sometimes I throw them away after having worked on them for many hours.)
My advice is to "chill": focus on the process instead of the result and let the posta take the time they take.
https://www.youtube.com/watch?v=EHqPrHTN1dU
you can see some others here
https://www.youtube.com/@GoogleJapan/search?query=%E3%82%AD%...
They had one with 1000+ keys but I don't see a video for it