Not a personal attack. Merely observing that he's coming off as someone I would not want to work with. This answers his tacit question of why they wouldn't accept his deal.
I gather that you didn't intend it as a personal attack, but we have to moderate by effects, not intent. By that standard, "how much of a pain in the ass you seem to be" is squarely in the personal attack category. Not a borderline call!
Turning down a job because your potential employer values arbitrary control of their employees over the actual value they created and being frustrated at the silliness of it is so normal. If this is "pain in the ass" behavior I can't imagine how milquetoast and ChatGPT professionalism your company Slack must be.
I'm legit sorry if that's how I'm coming across. Don't read tone in text, because there's no sharpness or self-importance meant at all.
I'm not sure how else to say what I'm saying. My qualifications are literally perfect for the job. My experience is perfect for the job. My location is perfect for the job. My attitude is perfect for the job.
It was billed as remote up to four days but the department head only allows 3. That was a deal breaker. I legitimately only negotiated on that. I was willing to take a pay and title cut because I agree with the mission of the institution.
I have always assumed that these are posted to obfuscate nepotism (aka successful networking). You make a show of searching for the just-right candidate, and in the meanwhile you already know exactly who you're going to hire.
>The inventor of the null reference refers to it as his "billion dollar mistake" because it "has led to innumerable errors, vulnerabilities, and system crashes, which have probably caused a billion dollars of pain and damage in the last forty years."
I've heard this Tony Hoare quote before, and it makes zero sense to me. If your reference is a number, your reference can be zero. How many billions of dollars have been saved by having a reserved constant which indicates "this is not a valid reference"?
How would I know that a pointer was uninitialized if this wasn't a feature?
It doesn't make zero sense to be, but I feel like it is strongly strongly strongly over-rated as a defect.
Yes it probably has lost us a couple billion in productivity by now, but I struggle to think of times this has had impact at any of the orgs I've worked at.
People love flipping out about js's weird implicit casting rules (the "wat") talk, but it too feels like one of these things that people will adoringly latch onto as a defect & use endlessly as some buge mortal flaw, even though it's an issue once or twice early in your codership when you didnt know what you were doign anyways then you are over it (and today, typescript & linters will shield you from harm here).
I don't want to totally write this shit off, but the negative antagonistic fervor & dogmatism people will adopt when they find some leverage to confirm their negarive biases is truly staggering, and an issue of great great social harm in my mind. Better advocacy against these issues would be welcome, but man, the discourse & discussion of these "defects" feels so uncontrolled & Dark Side rooted, not real, decoupled from the situation I feel on the ground.
This is a short-sighted and simplistic analysis of how land value works. I'm in a terrific location. Walking distance from the Texas State Fair and Cotton Bowl. Walking distance from Deep Ellum with all of its hip clubs and restaurants. Walking distance from downtown. Walking distance to the Dallas Convention Center. You can get to the Longhorn Ballroom, Southside Ballroom, and American Airlines Center in under ten minutes.
The only downside for buyers of the past? It was a poor neighborhood. All of those multifamily apartment complexes being torn down were full of poor people, mostly dark-skinned, many of them non-English speaking. Now that their landlords spent the past 15 years doing zero maintenance until they could get the buildings condemned and force all of the tenants out without needing to have grounds for eviction, they can sell the land, and it doesn't make any difference if the experience of actually living here gets shitty because of all the parties and not having any neighbors. The buyers don't care because the buyers don't actually live here. The single-night renters don't care because they don't live here, either.
I did not hear a complaint about what it was doing to their property values. I did hear:
> virtually nonstop construction of new housing, almost nobody lives here, the neighborhood is completely hollowed out, and all of these new luxury homes are mostly party houses used by rich college students and bachelorette parties.
Is it "flagging", though? Intel still seems to be pretty good at designing chips and their next gen laptop chips (made at TSMC) are allegedly more power efficient than the Snapdragon Elite (of course remains to be seen). It's the foundry that's dragging down.
If you look at the financial statements, it's quite the opposite however?
Their chips made on TSMC process are doing quite well and IFS has failed to secure worthwhile external customers and is losing money in their expansion hand over first.
The federal government is clearly ok with supporting a TSMC transition to the states. Something tells me though that they are willing to throw a lot of money at Intel if Intel is willing to fill the same niche that TSMC does currently.
That the chips currently produce more return than foundries is expected - it’s an established business. The foundries require much more up front investment. However the chips side of business has recently begun to show some cracks.
The foundries side of the business is in a different phase of life. It currently needs some TLC but has the potential to be totally ascendant at some point in the future. Assuming snapdragon is more interested in a chips business than a foundries business… it would just make sense to split them. There is tension with both under one roof as it is.
IFS has just announced Amazon as a customer with a design on 18A. Microsoft is also expected to tape out one design. They’re not going to challenge TSMC this decade, but becoming the #2 fab 2030 is achievable.
A few months ago, I played around with a contemporary build of preempt_rt to see if it was at the point where I could replace xenomai. My requirement is to be able to wake up on a timer with an interval of less than 350 us and do some work with low jitter. I wrote a simple task that just woke up every 350us and wrote down the time. It managed to do it once every 700us.
I don't believe they've actually made the kernel completely preemptive, though others can correct me. This means that you cannot achieve the same realtime performance with this as you could with a mesa kernel like xenomai.
>My requirement is to be able to wake up on a timer with an interval of less than 350 us and do some work with low jitter.
Cyclictest (from rt-test) is a tool to test exactly this. It will set an alarm and sleep on it. Then measure the offset between the time the alarm was set to, and the time the process gets the CPU.
With SCHED_FIFO (refer to sched(7)), the system is supposed to drop what it is doing the instant such a task becomes runnable, and not preempt it at all; CPU will only be released when the program voluntarily yields it by entering wait state.
Look at the max column; the unit is microseconds. There's a huge difference between behaviour of a standard voluntary preempt kernel and one with PREEMPT_RT enabled.
Linux is still Linux, and having Linux as a whole be preemptable by a separate RTOS kernel is always going to perform better in the realtime front, relative to trusting Linux to satisfy realtime for the user tasks it runs.
Incidentally, seL4[0] can pull off that trick, and do it even better: It can support mixed criticality (MCS), where hard realtime is guaranteed by proofs despite less important tasks, such as a Linux kernel under VMM, running on the same system.
reply