Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Material Theme has been pulled from VS Code's marketplace

github.com

Post reply on HN
Print view View original

211–220 of 424 posts

Re: Material Theme has been pulled from VS Code's marketplace

#211

Post by Macha »

Cthulhu_ wrote: post #198
TZubiri wrote: post #130

One of the things I love about the internet is learning how different people can be, I perceive it as different than me but I assume everyone has their quirks. In this case, this is one of the most extreme instances of people installing lots of dependencies. The moment I realized something was different in me was left pad, I already felt that couldn't be me. The log4j incident hit me different, it COULD have easily b…

A theme is fine - Google has been pushing Material for a while now, after all, so if you come from Google land the colours are familiar and preferred to you, same with themes like Solarized and whatnot. That said, I do agree that dependency management and reliance is a Problem these days. left-pad was the camel that broke the proverbial camel's back for many people, and it made people realise how ridiculous dependenc…

It had not occurred to me that a VS Code Theme was a full blown extension, since I've never installed one. I wonder if a lot of people have a mental model of a VS Code theme as a collection of CSS files, which should be relatively safe (even including those that install them).

Re: Material Theme has been pulled from VS Code's marketplace

#212

Post by tobyhinloopen »

jeroenhd wrote: post #184
dark-star wrote: post #108

Earlier quoted context omitted.

It's a common theme: - build an open-source thing - wait till thousands or millions of people are using it - change the license and close down the source - implement malicious code - push an update - profit! you now have your malware running on millions of systems

Should be added that the malicious part is often done by a third party that takes over an open source project when the original developer doesn't have the time/energy/money to maintain their open source/free work. Many Chrome extensions end up being sold for thousands or just hundreds of dollars because there's no money in them and the dev isn't all that interested. Society as a whole could easily avoid this by fundi…

> Society as a whole

As long as we won't have to pay 2 USD for an extension!

Re: Material Theme has been pulled from VS Code's marketplace

#213

Post by Macha »

skrebbel wrote: post #207
koakuma-chan wrote: post #80

Earlier quoted context omitted.

I haven't noticed any difference after tailwind started using oklch, doubt there's any.

The question isn't whether you noticed a difference, but whether your aunt notices a difference on her 7 year old Chromebook

oklch should be an incredibly minor to unmeasurable performance hit, even on a 7 year old chromebook. Nor should it affect the displayed output. It's just a better color picker syntax.

Re: Material Theme has been pulled from VS Code's marketplace

#214

Post by card_zero »

wizzwizz4 wrote: post #205
card_zero wrote: post #192

Earlier quoted context omitted.

Would that change if cars could go fast enough, say mach 3?

When driving, you want to keep your velocity relative to other cars as low as possible, while retaining your ability to avoid obstacles / not murder cyclists and pedestrians. If cars could go at mach 3, then you'd want to avoid roads entirely: it's not feasible to avoid obstacles at that speed, and you certainly don't want to get hit by shockwaves or – worse – actual cars travelling at such relative velocities. So no…

Yes, or relativistic velocities. I figured that harm due to the energy of the collision is limited by death, while time spent on road tends to zero, but your mention of shockwaves brings to mind that a sufficiently high-energy collision would also be a danger to otherwise uninvolved road users, or residents of nearby towns, so my first assumption was incorrect. (I leave aside the problem of maintaining control of a mach 3 road vehicle as an implementation detail.)

Re: Material Theme has been pulled from VS Code's marketplace

#217

Post by [deleted] »

isidorn wrote: post #79

Hi - Isidor here from the VS Code team. A member of the community did a deep security analysis of the extension and found multiple red flags that indicate malicious intent and reported this to us. Our security researchers at Microsoft confirmed this claims and found additional suspicious code. We banned the publisher from the VS Marketplace and removed all of their extensions and uninstalled from all VS Code instance…

[deleted]

Re: Material Theme has been pulled from VS Code's marketplace

#218

Post by hombre_fatal »

jeroenhd wrote: post #184
dark-star wrote: post #108

Earlier quoted context omitted.

It's a common theme: - build an open-source thing - wait till thousands or millions of people are using it - change the license and close down the source - implement malicious code - push an update - profit! you now have your malware running on millions of systems

Should be added that the malicious part is often done by a third party that takes over an open source project when the original developer doesn't have the time/energy/money to maintain their open source/free work. Many Chrome extensions end up being sold for thousands or just hundreds of dollars because there's no money in them and the dev isn't all that interested. Society as a whole could easily avoid this by fundi…

Every time piracy or Youtube ads come up, HNers grandstand on how they don't even pay a dime to the content creators making the hundreds of hours of videos they watch.

GGs if you want a buck for the VSCode theme you made.

Re: Material Theme has been pulled from VS Code's marketplace

#220

Post by dingnuts »

Cthulhu_ wrote: post #182
misnome wrote: post #155

Earlier quoted context omitted.

Yeah, the vscode release notes used to be lists of interesting new things and novel improvements. Now they are all “copilot” “features”.

TBH, no criticism on the developers, but the VS Code release notes haven't been interesting or relevant to how I used the editor for years. I think I checked out when they added a terminal client to it and it dominated the release notes for ages. AI features is one of the bigger innovations in editors in years, I fully understand the enthusiasm, especially given it can be linked to an earnings model. That said, befor…

This is why I use Emacs and it's why I didn't stop using Emacs when Sublime Text II, then Atom, then VSCode became popular.

When Microsoft gets bored of VSCode or forces you to only do AI "vibe coding", Emacs will still be there.

New version just came out. The release notes were full of good things.

Post reply on HN