Hacker News new | past | comments | ask | show | jobs | submit | Longlius's comments login

For the same reason we disallow severe product dumping - it's a ploy to build marketshare in an attempt to become hostile to consumers down the road. We don't let companies dump products for a reason.

>thunderbolt (usb c) is owned by Intel.

USB-C is distinct from Thunderbolt. And Thunderbolt itself got rolled into USB4 which is now an industry standard rather than one controlled by Intel.

Even so, Intel and AMD aren't so hostile to each other to avoid cross-licensing when it's mutually beneficial. A lot of the newest generation of AM5 motherboards actually include an Intel chipset for handling Thunderbolt/USB4.


This. By definition, you can't outgrow your customers and yet we continue to see exporting countries try to outgrow their consumer counterparts simply by doubling down on exports rather than transitioning to consumer economies (or worse - trying to supplement exports with bad investments).


This isn't talking about 'unlimited growth.' It's talking about sustaining our current population structure or even tapering it off gracefully rather than facing the steep decline we're dealing with now.


Global population is not declining. It is projected to continue growing for at least another few decades.


Or dangerous agricultural work like picking and processing tobacco.


A basic coding interview doesn't really cover what companies are looking for. There's a lot of talk about devops and cloud development, which means they're looking for people who are already familiar with developing software that's cloud native rather than just general software development ability.

At my day job, we actually spend a significant amount of time working with juniors to get them up to speed on deploying to kubernetes (writing manifest/helm files, building cloud-ready configurations, handling autoscaling etc). The company I work at sees a lot of value in investing senior engineer time into teaching new grads the ropes but I feel like a lot of companies would rather just hire people who already know how to do this stuff.


I don't really know how you'd usefully learn any of that unless you already needed to figure it out at some point while on the job.

I'm not a junior, maybe intermediate-senior depending on how one sees it, but I'm definitely seeing these requirements in a ton of jobs, but since I've largely been working frontend in the last few teams I've been a part of.

I know that I need to pivot back to more of a full-stack kind of situation, and I'm working on rebuilding those backend skills, but at this point it feels like I've already missed the boat.


Only ~70% of Americans read at least one book a year.


Is that an entire book or any part of any book? Does it count audiobooks? I know a lot of people who claim to "read" a lot of books, but they actually are listening to audiobooks.


That's a suspicious statistic in my opinion and feels like something people would like about on a self reporting survey lol.


It's functionally the same - code signing is mandated unless you want your users to get a scary pop-up.


It is definitely a different experience - the Windows warnings are very easy to not take seriously, since they pop up for anything and everything. On MacOS, you have to practically agree to your PC being unsafe to even enable running non-signed code, iirc.


Most blue checks I've encountered are just intentionally engaging in bad faith discourse to farm engagement for the payout, so being able to identify the accounts that can do this is a positive in my book. I tend to block most of blue checkmark accounts reflexively.


X is now giving premium status—including the checkmark—to users followed by a sufficient number of existing blue check users.


I don't even think it's necessarily moderation so much as maintaining these high-traffic projects is now akin to a full-time job minus the pay.

At a certain point, companies need to step up and provide funding or engineering work or they should just keep expecting to get owned.


If there is a larger shift to companies paying for the software they rely on that is currently free, it's not going to be companies paying open-source maintainers, it's going to be companies paying other companies that they can sign contracts with and pass legal responsibility to.


Why would they when they can just... not?


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: