Laches comes to mind. If it takes you twenty-nine years to decide that you think a program is unconstitutional, you have lost your right to litigate.
This was very clearly a "We don't like this, and we're going to try to find a way to strike it down in court so that the courts get blamed instead of us" move. All but three of the supreme court justices saw through it as a transparently obvious political ploy.
1. Decide what you want. lots of money 2. Decide how to get it. rob a bank
= good decision
You can make good decisions if you follow this one simple rule Don't listen to randoms on the Internet.
Clearly, the second rule should be "decide the best way to get it".
2. Learn how to rob a bank and hire yourself out as a bank security consultant for a million dollars per job on the condition that you successfully rob it.
You still rob the bank, but you don't keep the money, you don't go to jail, and they pay you a lot for showing the flaws in their security system. Repeat a few times. Retire.
Bottomline: IQ is overrated.
I would argue that it is merely poorly understood and reacted to at face value only. No depth to the perceptions.
Look, my IQ has been tested and it is very high... and yet somehow or another, "normal" people show me to be quite stupid often enough to eliminate much of my ego.
I have met people an order of magnitude smarter than me... and yet somehow or another, I end up reminding them to be humble.
Yeah, that's the thing. Nobody has all the right answers, because nobody can ask the right questions every time. Nobody knows everything, and there's always that one thing you didn't think of that, when someone points it out, makes you rethink everything.
The difference between smart people and not-smart people is that smart people probably point out those things to others more often than the other way around.
Sometime, if we are lucky, we will get a small programming language that does not collect new features every year just for the sake of progress
Swift does get new features every year but I would argue most have been good quality of life, or quality of code improvements. Especially the latest changes around concurrency are really good.
Avoiding the pyramid of 500 third-party packages for a mid-sized application is a good thing.
Totally agree but that is where Swift has been really great! It is VERY practical now to build a medium to large application with only handful of third party packages. That was very much not the case 5-10 years ago. If you look at any modern Swift app it looks nothing like the swirl of madness that is a modern React application.
???
Other than the SwiftUI framework, approximately everything that's in Swift was in Objective-C 5–10 years ago. It was very practical to build a medium-to-large app back then with few or no third-party packages, too. React is almost always a mistake for native apps.
Except this wouldn't actually solve this. You'd be able to share the business logic, which would be a benefit. But you wouldn't be able to share any of the UI, system, or OS interaction code which is where all the incompatibilities come. If you just wanted to share business logic, there were already ways you could do that (write it in C would be one way).
Also, if they really wanted to do that, they should consider going the opposite way and bringing Kotlin to Swift. Kotlin also has a significant server side use that's growing (mainly by replacing Java), Swift is iOS and Mac only. They'll find a lot more people willing to learn Kotlin than Swift. Of course Apple won't consider that due to NIH and control issues.
Nothing inherently prevents Apple from porting SwiftUI to Android. It would probably be enormous, but...
Still wondering about those upload speeds, though.
It's kind of a complex question. It depends on where you are and what plan you currently have.
If you're in a mid-split area (where Comcast is using a larger range of frequencies for upload traffic) and had a plan to take advantage of it - which it sounds like you are - then the new plans actually regress on upload speeds. The old ~1Gbps and ~2Gbps plans had 300Mbps nominal uploads (closer to 360Mbps due to overprovisioning), while all other plans were 150Mbps nominal. The new plans drop this down to 100Mbps nominal for everything except the new ~2Gbps plan, which gets 250Mbps nominal.
Unfortunately, you're facing an either/or proposition. Comcast won't remove the data cap for existing plans, you have to transition to a new plan. But if you do that, then you'll get the new, lower upload speeds. With that said, Comcast isn't forcing anyone to upgrade, so current customers can stay on their legacy plans indefinitely.
This all sounded great until the word "catheter"!
!!!
then I crossed my legs, and knocked my computer on the floor.
Sounds like Apple is just trying to find another way to sidestep a judicial order to me. Apple shouldn't have any right to charge a core technology fee or a commission on sales that they aren't involved in.
If Apple wants to charge a license fee for using Xcode, they can go for it, but they shouldn't be surprised if everybody stops using it.
Beyond that, though, Apple charging any fees in any form to any company that distributes software directly seems nonsensical and contrary to a reasonable interpretation of the law. Apple should really stop trying to avoid their responsibilities under European Union law, because the more games they play, the bigger the fines are going to be, and as a stockholder, that nonsense really annoys me.
If there are still enough suckers willing to pay for a Playstation Plus subscription even without the newest games, and if you can then sell some of those games to some of the people who have the subscriptions, that's free money. The only thing that would likely make a real impact on that would be if they saw their subscriptions start to decline and single-title sales increase after some major title came out.
So if you want to make that policy change, pick an upcoming title and convince about a hundred thousand of your friends to all buy that title on release day and drop their Playstation Plus subscriptions on the same day.
It's only a single lane of PCIe, so the ~32 gigabit total throughput is probably not realistically enough for 6 links at 5 gigabits each
Should be close enough. PCIe overhead is about ~0.6% for the framing, and it's 128b/130b coding.
I was factoring in IRQ latency and the CPU overhead of handling the interrupt into my thinking, and assuming that some non-small percentage of the time would not be spent actively pulling data off of the bus, meaning that if you really want to saturate the bus, the bus would likely have to markedly exceed the total throughput even with hardware DMA pushing data from the device side. But I guess it depends on what the devices on the bus are, whether it is isochronous traffic or just async, etc.
>Yeah, why would a city government want to ensure they can
>accurately read/display their last few DECADES of official, legal
>documents?
If they're concerned with that, they should *avoid* Microsoft, unless they are going to keep an old machine with each version forever.
Historically, staroffice/libreoffice/openoffice has done a *better* job than ms of reading prior versions of ms documents.
but you're not removing that interest--you'er just changing who pays for it.
"public finance" isn't free, nor does it mean that the money doesn't get borrowed. Rather, the net increase in public debt is the amount paid out by the government.
The job ad lists four languages, JavaScript, TypeScript, GO and C#. JS/TS are required because we work in Angular, GO and C# are only "Nice-to-Have", and I don't bother listing HTML / CSS because if you know JS/TS, you're good to go. That's a simple development language stack, you need to know JavaScript or TypeScript, and have used Angular, or a close enough framework, I'd honestly accept React.
At least 50% of the applicants were Java developers, not JavaScript, Java!
To be fair, if you can code in Java, you can code in TypeScript or JavaScript. I mean, the object declaration syntax is an abomination, but other than that, there's nothing super complex about moving from one object-oriented programming language to another, though you may get non-idiomatic stuff. (As they say, "A good Java programmer can write Java in any programming language.")
At least 25% used the term / number method, where you include every term you've ever heard, or throw around numbers like 25%, 50%, 40+, in hopes to pass an AI scanner. 75% of the resumes were junk before I started, but I have a policy to read every single resume from every applicant. Out of the last 25%, or 43 resumes, 30 of them had serious spelling / grammar errors, and not "You used American English, not Canadian English", actual errors. A few misspelled "English", some of them had term names wrong, like Angueact, or Axure, and others had missing date ranges, bad formatting, bad colours, contrast issues, and so on.
That's sad.
Out of the resumes that include portfolio sites, or personal sites, most were broken, some had TLS errors, and except for two, they were hosted on a site builder. Out of the resumes which included GitHub / GitLab links, except for three, showed no work, were missing, or, were forks of other projects, and they didn't clean their fork up.
It's probably worth noting that anyone with experience in industry probably doesn't have a portfolio site, so if you expect that, you'll be limiting yourself to new grads. If you like weird code related to PTZ cameras, I have a couple of coding-related personal projects on the side, but I can't show you anything else that I've worked on since I started in the industry other than some developer documentation (which many other people have worked on over the years since I last touched it). I doubt I'm alone in that.
At some point, folks do coding interviews because seeing how people approach writing code is the only way to know if they can write code. And it has to be done in person, or else you'll be finding out how good some AI is at writing code instead more often than not. And that's expensive, which is why people who don't live physically in the area you're hiring are challenging.
I could keep going, but the main issue I'm getting at is we had no bubble QA, and so many of the people who graduated, found work, and then got laid off, aren't worth hiring.
And this is why I suspect you're missing a lot of good people. As many people as have gotten laid off, most of whom were working successfully at other companies, they can't mostly be useless. Maybe they will take a little bit longer to come up to speed on whatever framework you're using, or whatever language you're using, but rejecting them out of hand for that is a bit like not hiring a construction worker because they've only worked with DeWalt tools and you use Makita.
It's difficult to fake skill, if your skill review is being done by someone who cares, and has knowledge to call you out. When you say you're "detailed oriented" (never put that in a resume), and then misspell "English", include a GitHub that is all forks, showing no work, include a personal site, you didn't make, and seemingly have used every technology that ever existed, while improving processes by 100 000% in two days, what do you expect to happen?
Yeah, the obvious fakes are obvious. I don't know who they think they're going to fool, other than AI-based résumé scanners, and if someone lies on their résumé and gets caught, they'll still get fired even if they were working at the company competently, so they're really not doing themselves any favors by pulling stunts like that.
As for me, my résumé also includes my music background. It is surprising how often that gets noticed and has even ended up being part of interview questions at times. It may not get you past the bot scanners, but you never know.
As for compression..... I have little experience with USB camera modules, but I know that MJPEG is a normal feature on them, which would get you 1080p60 (24bpp) for about 80Mbps per stream.
It's true that a Pi is only 5Gbps for its onboard ports, but with the PCIe, we can slap USB3.2 on it pretty easily. That's a little bit custom, but then again we were talking about slapping 6 XHCI controllers on something.
It's only a single lane of PCIe, so the ~32 gigabit total throughput is probably not realistically enough for 6 links at 5 gigabits each, but then again the Pi's CPU probably can't handle the traffic from six saturated USB 3 links, either.
Traditional vocational training (welder, plumber, electrician, etc) are likely to be more financially viable than a CS degree these days. Those seem a bit more resistant to both Skynet and bottom feeder labor taking over your work.
I think that a majority of welding in the manufacturing world is already done robotically these days. Given modern AI advances, it stands to reason that this will become more widespread in construction and other areas sooner, rather than later. I would be surprised if you could make a 50-year career of it at this point. I'd give it twenty years before the work starts drying up.
The same is true for plumbing and electrical work, but less so, because there's so much more of that, and so much of it is bespoke, making repairs a bit more challenging. Even still, you'll have robots doing a lot of the work by the time you retire, just maybe not all of it.
How much net work could a network work, if a network could net work?
