Somebody needs to get on deduplicating UTF8 ASAP
I’m only still here because account deletion is broken on KBin.
Somebody needs to get on deduplicating UTF8 ASAP
That’s reasonable. I pulled that info from Wikipedia, and I don’t speak Japanese, so I just was going off that.
That’s great and all, but for those of us that do speak English and are expecting certain grammatical norms, eschewing those norms, regardless of the validity of the reason, makes it significantly harder for us to parse.
The question mark is not a rare piece of punctuation, either. It’s used in China. It’s used in Japan. It’s used in Vietnamese, every Romance language I’ve ever encountered, and every Germanic language I’ve ever encountered. I’m not saying I understand all those languages, but I can certainly recognize when someone’s asking a question in one because the question mark remains the same.
This is a piss-poor excuse and reeks of the attitude of one who’s never encountered a language that doesn’t use the Latin Alphabet even in passing. Oh yeah, by the way, it’s called the Latin Alphabet, not the English Alphabet.
I actually disagree with point 1 to an extent. The startup work for such a machine would indeed require a lot of effort, but once that groundwork is in place, wouldn’t that make it easier to maintain momentum and release a successor?
Not much, dollar, how about you?
Hey man, it happens. I could tell that you had some valid arguments in there, I was just trying to get you to express them. I definitely didn’t help by joining in the immaturity either.
Side note, I’m legit starting to hate my Tesla anyway, but I wasn’t about to admit that yesterday lol. There are absolutely a lot of valid criticisms of them, I just think the majority are overblown, especially as they relate to FSD. I’m in the beta and it’s basically the only reason I still have the damn thing.
Anyway, I’m sorry too. I probably should have just walked away when things got heated, but there was a part of me that was secretly hoping to see how long we’d keep going back and forth calling each other assholes because I thought it would be funny.
NGL, my first comment was partially meant to see if you actually had blocked me lol
You know what I bet we both agree on? Limited liability in general being a shit idea.
Yeah it really comes back to “fines are only for poor people.” Google can just count the fines as the cost of doing business while simultaneously leveraging their dominance to force other companies to break regulations in order to work with them.
See, I figure all of those things would be accounted for in whatever civil suit gets brought against the company. Frankly, I think that’s much more fair to companies both big and small because it involves a group of people working together to figure how much of a fine to levy in each individual instance, rather than having a blanket policy that may or may not account for edge cases. If the company is huge and the fuckup egregious, then the jury is (theoretically) going to throw the book at them.
At the very least, I’d want a jury in between the company and whichever government body is fining them, because regulatory bodies are prime targets for corporate shills to take over and it’s harder for that to run rampant if you have a bunch of regular jackoffs acting as gatekeepers.
There’s also the issue of ongoing compliance for small companies. Cybersecurity engineers are not cheap, and being all but required by law to employ one could (1) drive small companies out of business (180k a year may be cheap for Facebook, but it’s definitely not for Joe Buttsniffer and Sons Catering), and (2) cause market saturation so bad that the average salary makes nobody want to do the job anymore.
When you say “corporations,” it seems like you’re exclusively counting companies like Google, Meta, etc, whereas I’m also including the mom and pop, 15-person operations that would be impacted by the same regulations you suggest. Those underdogs are the ones I want to protect, since they’re the only chance the world has at dethroning the incumbents and ensuring that the big guys don’t outlive their usefulness.
Your bridge analogy falls apart because there already are standards (FIPS, among others) that are shockingly insecure despite having been updated relatively recently, and yet we still have breaches. If the standards were effective, places like AmerisourceBergen, the country’s largest pharmaceutical distributor, wouldn’t be supplementing them with additional safeguards. No standard is going to work perfectly, or even particularly well, for everyone. Bridges still fall down.
EDIT: Alternatively, there would need to be a provision that allows companies to sue the government if they get breached while following their standards, since it was the government that said they were safe.
And I’ll counter with this: no system is perfect, especially when major parts are made by non-employees. Mistakes can and do happen because corporations, regardless of size, are made up of humans, and humans are really good at fucking up.
I did miss that, but again, it’s additional fines on top of an almost guaranteed lawsuit for something that may not even be their fault. If they got owned by a Heartbleed exploit back when it was first announced and a fix wasn’t available yet, should a company be responsible for that? What about when they get hit by a vuln that’s been stockpiled for a couple years and purposely has no fix due to interference from bad actors? There are a lot of situations where fining someone for getting breached doesn’t make sense.
Ok then, how about considering that this will only serve to benefit the big tech companies because they’re the ones that can afford the fines? A breach is usually enough to make a smaller company go out of business already between cleanup and lawsuits. Why make it easier for the big tech companies to maintain power?
It’ll also screw over anyone trying to break into the market, ensuring that the big tech companies remain unchallenged indefinitely.
This is the stupidest idea I’ve ever heard. You don’t fine a bank for getting robbed. This reeks of frontend engineer idiocy, which is ironically the exact type of idiocy that tends to cause breaches like this.
Apple might as well be a fashion company at this point.
Spoken like someone who clearly hasn’t been practicing. Get gud.
Not to mention, it’s a standard now, and the old Supercharger protocol is being phased out in favor of another standardized one (I forget which). Further development done on their chargers from here on out is going to be done by a consortium of companies rather than in-house anyway.