The thing about Bun that turns me off is around the OS-specific system call optimizations (using different optimizations for different platforms) which means that each new feature they add to bun that uses any system calls must be done 3 times for the 3 major platforms (MacOS, Windows, Linux)
Another thing is I believe Deno supports WebGPU and Node supports WebGL via Angle etc (for e.g. running Tensorflow with GPU support)but Bun not only has no story there but its author has refused to provide any info about their intent aroundGPU support.
The thing about Bun that turns me off is around the OS-specific system call optimizations (using different optimizations for different platforms) which means that each new feature they add to bun that uses any system calls must be done 3 times for the 3 major platforms (MacOS, Windows, Linux)
it might drive some skepticism toward long term support or reliability ( everything has to be developed three times ) and unknown performance characteristics ( or even potential behavior ) across platforms.
not sure I agree with the take, but that's how I read it
It's surprisingly easy to develop OS-specific code using Zig (the language Bun uses), because of its excellent integrated support for cross compilation and comptime feature. For example, with some zig code I write (a posix layer for node), I build for many platforms in parallel every time I make a change.
the metadata can be versioned and you can lookup by version, so names of stored file can be changed but every time there is a change to any of the metadata the version is updated too
in tech, we don't really have 40hr/wk. It's more like 80hr/wk. And work on weekends. If you have a position that requires 40hrs/wk or less and no work on weekends whatsoever, consider yourself lucky. I hear stories about colleagues being overworked on continuous basis.
Speak for yourself. The vast majority of engineers I know (in the US and Europe) don't do more than 40 hours a week and without weekends, and oftentimes many work even fewer hours, perhaps even 20 hours a week. There are also so many jobs that if you're truly doing more than 40, that's because you want to or at least haven't bothered to start looking to switch jobs.
> If you have a position that requires 40hrs/wk or less and no work on weekends whatsoever, consider yourself lucky.
That's backwards. If you have a position that requires over 40hrs/wk, or any weekend work without overtime pay, consider yourself exploited (and if you're doing it without it being required, consider yourself a scab). Join a union, quit that job, or both.
Somehow, I've managed to work 40/hr week or less at all of my jobs.
Recently, due to a disability, I've been limited to a max of 40 hr/wk with a restricted schedule (M-F 0800-1800). Unfortunately, I can't do on-call and no matter how severe an incident is in the middle of the night, I'm not available.
No one has an issue with this. In a funny way, it's good I'm on the team because we're always testing the "Kayodé bus factor". Thus far, it's been more than 1.
That is most definitely not the case in Australia. I'm a dev, I never work weekends. I do sometimes work later in the day meaning some weeks are probably a bit more than 40 hours, but I also take long lunch breaks or leave early so some weeks are also probably slightly less. This is the case for all the devs I know as well, and more than a small amount of regular OT is seen as cause to quit and get work elsewhere.
There is an exception for dev managers, who seem to work longer hours generally but definitely nothing approaching 80 hours
In countries where labor laws are strong working more than 40 hours a week in a salaried role is not common. And when there is overtime, it’s often taken in lieu and expected that you get those hours back out of your regular day.
If you have a position that requires more than 40 hours a week regularly, do the math on your hourly rate, and look at hour its affecting your health. If you’re under 25 you’ll probably get away with it, if not the second order impacts on your life are not insignificant, and can make you less productive.
I don’t know anyone who does much over 40 hours in the UK, let alone anything close to 80 hours. A few might pick up urgent tasks on the weekend, but only when needed and not regularly.
I think also depends where in the US. In Seattle, a lot of tech workers are with Amazon. When I worked with Amazon, over two years, there were perhaps two weeks total where I worked less than 50 hours. In that job, and in several that followed, the office was for collaboration, meetings, maybe an hour of actual work, and then at home was where the second workday began in a quiet setting & you put in 3-5 hours additional coding (plus whatever on-call threw at you).
I've worked for US companies on their EU offices for nearly 10 years, and there's definitely much less of it here, but I've definitely ran into some US employees who have been less than impressed at how unavailable I am outside hours in that time
I read that Tim Cook has a weekly Sunday evening meeting with his staff; this seems reasonable, since that time might otherwise be wasted on family, friends, or home responsibilities - rather than taking care of critically important Apple business that can't wait until Monday morning.
Sunday evening in California is Monday morning in Asia - if you wait until Monday morning in CA to start things off you burn a whole day.
Now, I doubt Tim is happy with people leaving early on Friday afternoon either - but given Apple’s business and the importance of the Asian supply chain, a Sunday evening meeting is justified.
Also anyone reporting directly to Tim Cook is being paid tens of millions per year for their trouble…
You should really try to find a new job. Crazy hours outside of some startups and super high paying jobs in a few sectors are not the norm in tech. Most people I know in the industry in NYC work 35-40 and do just fine.
What if the task was invoked asynchronously (and maybe it keeps happening.) What does async stack unwinding entail in Rust? Is there a parent-child relationship between invoker and invokee? async scopes (https://rust-lang.github.io/wg-async/vision/roadmap/scopes.h...) ? I've not touched Rust at all.
Unless it was holding a welding gun and stopped on one spot with the welding flame turned on instead of gracefully turning off the flame and backing away.
Never used Rust before but is there a way to supply some default code to run in such a situation instead of just not carrying out the bad operation?
The way our brain is equipped to process concepts is an over-simplification and confusing of what some refer to as the deeper reality or simply the reality that our mind obfuscates. It's worse than Plato's Cave.
It's futile to opine on things that we don't yet fully comprehend in the greater scheme of things. We don't even know (yet we think we do) what we're opining about.
Good luck with all such feeble attempts at deciphering reality.
No, this was not written by a bot, and I am talking about Bitcoin.
No, not the thing itself. Humans are fixated on the thing itself. I couldn't care less about the Dorkchain, but what role it plays in the greater scheme of things. Be it bad or good from your individual perspective.
In Arabic, Sunday is Ahad (first) Monday is Ithnain (second) and so on until Friday which is Jum’a (gathering) and Sabit (comes from Sabbath I think?) as Saturday.
So the US is not the only country that considers Sunday to be the first day, etymologically speaking. I think the first day in the Middle East is Saturday because people work on that day (on Friday is a day off, unless things changed since the 70s)
Another thing is I believe Deno supports WebGPU and Node supports WebGL via Angle etc (for e.g. running Tensorflow with GPU support)but Bun not only has no story there but its author has refused to provide any info about their intent aroundGPU support.