I always use wildcard import for utils, because I write my JavaScript the lisp way, by combining many utils together. I have a ton of utils, importing them one by one will take a lot of room. This wildcard doesn’t mess up tree shaking because every single util is used at least once within the project. If something’s not used, I delete it

@Grumm fidewhat? We’re polyamorous

@devJs WASOWASOWASOWASO

@devJs BITCONNEEEECTUUUUUU

@iiii it doesn’t have telemetry

@Root yeah, полигон, the place where shit gets blown up

@iiii vscode is a wrapper of vscodium with added telemetry

@TerriToniAX vscodium is better

@cafecortado my brain doesn't have enough computational power to emulate speech or writing.

Imagine your corpse being blown up by some new AI drone-powered homing missile into small pieces that probably won't even be scraped off the polygon sand and buried.

@djsumdog nah, I quit starving like a month or so ago because it fucked with my mental state to the point that I'm still recovering

@CoreFusionX good enough for home lab, but not good enough for a client-facing service that will cost me money if it goes offline

especially given that power outages are common where I live

@iiii or, I can spend some time there to target everyone

@iiii oh, all sorts of things!

@iiii no one is rational 100% of the time. I can totally see people who frequent their favorite coworking space get used to the convenience of leaving their locked laptop on their table while they go to the bathroom, and forget that it's a public space.

Why not prevent the issue once and for all by installing usbguard? It's free and open source.

@antigermanist if someone came to you there and inserted a usb stick into your laptop, your brain would've probably erased the memory of that because of how unusual it was and how much processing power was needed to process it correctly. Are you sure no one attacked your laptop like this ever?

@12bitfloat he also made a drone that automatically approaches other drones, hack them and build an army of drones for you

@iiii you're working in a coworking space. You want to go to the bathroom, so you lock your laptop and go. You know it's locked, so no one can access it. In the meantime, I connect to your usb, wait 30 seconds and disconnect. You never notice.

@antigermanist if you never leave your home with your laptop then sure

@antigermanist someone else will

btw, if the name "Samy Kamkar" does ring a bell, you're not tripping: he was behind that famous MySpace exploit that made people's browsers add Samy as a friend, making him the person with the most MySpace friends in no time.

@tosensei z-index: π;

@donkulator ouch

@donkulator Max Miedinger wants to know your location

@12bitfloat wow. I spent so much time convincing people that uncle bob is a moron that I basically gave up. Clean code to software engineering is what tailwind is to css -- cancer.

@TeachMeCode lol it wasn’t material. Material is google, not hp

@retoor if course it would. First, they make Chromium closed-source. Then, they replace HTTP with something proprietary. Then, their telemetry will be mandatory and won't show in devtools/be blocked by extensions.

@azuredivay I don't care about CSS libs. I do everything myself. All CSS libs suck and they're fucking ugly, except for one obscure React UI kit made by HP (of all people) that was deprecated around 7 years ago. It's a bummer that I can't use it because I quit doing react

@12bitfloat ouch

@devJs I consider iOS Safari to be the ultimate litmus test for hacky code. Chrome is good at absorbing hacks, while Safari is more strict and exact. For example, it shouldn't be possible to synchronize positions of two elements while they're being transitioned, if one of them is moved with translate() and the other one with margin. Chrome will sync them up for you, Safari won't, because that's lowkey a hack, and you shouldn't write hacks. If you need animations to sync, animate the same exact property. Use translate() everywhere.

If my site works in Safari, I know it works everywhere. From my 10 years of experience, every "bug" that people attributed to Safari was actually their code's fault, sans some quirks that I can name. For example, Safari's 100vh, as well as position: fixed's data is not necessarily equal to the viewport data you can get with JS during and after the on-screen keyboard is being collapsed, so your fixed elements can get stuck mid-air. But thats about it really