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

Hey Jarred, big fan of your work on Bun.

Until recently I've been using Deno (mostly to avoid using Node and the tooling hell that entails) and it looks like for my use-cases Bun is getting there. I've had a pleasant experience using Bun as the basis of a test harness.

Here's my question (with a tiny bit of lead-in):

What I like about Deno is the integrated LSP (reducing tooling hell), are there any plans for Bun to feature this too? Bun already internally transpiles TypeScript which is great but having the LSP bundled too would give this single binary integrated experience a boon I feel.

Looking forward to Bun 1.0!

P.S. I'm starting to stretch my Zig muscles, you looking for Zig developers? ;)


Friendly warning about expected working conditions: https://twitter.com/lukeshiru/status/1563493902560428034


I don't understand the hand-wringing about this. Bun explicitly says, they are a small team working very hard on some hard problems. If that's your idea of a good time, you're free to try and join. If you want a chiller job, there's 1,000 of them out there. It's not like Jarred is some corporate overlord demanding people slave for him while he sips margarita on a beach... he just wants people working on the same frequency as himself.


There's a school of thought on work life balance which amounts to wanting just enough life overhead to support the work. That 'balance' is not for everyone - but crucially it is what some people want.


Companies wanted to say they have "work / life balance"; rather than change their practices, they expanded the definition of work / life balance.

By this definition, is there any company that doesn't have work / life balance? By this new definition you propose, does the term mean anything?

Is 996 a good work life balance because "it is what some people want"?


>That 'balance' is not for everyone - but crucially it is what some people want

I've never seen anyone that could sustain an 80+ hour per week grind and make it out without severe personal issues (whether they are willing to acknowledge it or not). I've seen many, many incredibly talented people burn out and suffer permanent health or career damage to hit their short-term goals. I personally know an otherwise healthy 30 year old swe who had a stress related heart attack. It may be what some people want but you can't grind your way out of being a human.


But are they compensated or are we dealing with disguised wage theft[1]? A lot of times, when it's time to pay all that overtime or when someone finally speaks up about it, suddenly the "fun" stops.

Then there is the not speaking out, resulting in: 1) Burn out and quit. 2) Company dumps or fires them after burning them out. Then does the same to the new ones. Until something obvious or tragic stops them. 3) Quiet destruction of personal lives. Sometimes leading to significant health and/or mental problems, related to stress, and even suicide in some cases.

Balance is necessary, because otherwise it can be like playing with fire. It's all "fun and games", until people get or realized they got burned.

[1]: https://en.wikipedia.org/wiki/Wage_theft


New product teams are a grind, but with the right people, also a lot of fun. It isn't for everyone. When I was hiring for a NPT working on cutting edge tech I told everyone I interviewed they the work life balance was super skewed.

The people who accepted job offers self selected for having a passion for pushing technology forward.

I tried to keep things as sane as I could, but I'd have to go in on weekends and usher people out of the office.

For some people, building cutting edge things is /fun/.


How is this relevant to the comment you're replying to?


He's asking to be hired by the company behind Bun?

How <<isn't>> the previous comment relevant?!?


You can pretty much use tsserver with bun-types and get most if not all the features you get from deno-lsp. I know because we provide both deno-lsp and tsserver for windmill.dev to provide intellisense over websocket/jsonrpc for our monaco webide at windmill.dev and it works great :)


Fines should be at least 100% of _revenue_ from these activities to actually punish the business. At the very least 100% of _profit_ from the activity. Anything less is cost of doing business since it's by definition a net profit.


This is the most disgusting thing I have ever read. My blood is boiling to the point where I genuinely don't see a bright future.

Ben Wiser (Google), Borbala Benko (Google), Philipp Pfeiffenberger (Google), and Sergey Kataev (Google) have got to be the most repugnant people on the planet for pretending this is anything but a scheme to destroy all privacy and freedom on the web all so fucking Google can sell more ads.


Location: Melbourne, Australia.

Remote: Yes, hybrid is also fine.

Willing to relocate: Yes: U.K (I'm a citizen), South Korea, Japan, Germany, Singapore, France, The Netherlands, U.S., or within Australia if it makes sense.

Technologies: {Java,Type}Script, Ruby (on Rails), Node/Deno, React, SolidJS, AWS, Azure, .NET, C#, F#, some C and Zig, POSIX Shell/Bash, some Python, Terraform, Ansible, SaltStack.

Résumé/CV: https://www.linkedin.com/in/tsujp/ (email for full PDF, references) and https://github.com/tsujp

Email: jc [plus] j [dot] yc [at] wz [dot] ht

I do DevOps and Software Engineering (particularly full-stack web but increasingly more systems programming). I will happily learn new technologies and enjoy learning in general as well as partaking in challenging environments where application of knowledge and skills solves problems.


The changes should be the main meat of most commit messages and if the intent or other options considered add value to that then they should be included below.

The reality is if the intent, other options, relevant notes etc are not valuable then they will be lost to time (no loss). If they are valuable where else are you going to put them? Some wiki or knowledge store for your project? How will you know that this specific commit and that (probably) sparse text in said knowledge store are related? Why not just put them together where they belong anyway.

Commit messages are not valuable when they are maximally short. They are valuable when they describe the changes the commit applies and ANY other relevant information for people (including the author(s)) in the future so that said people can understand the commits effect and other relevant information.

For an example of amazing commit messages look at PostgreSQL’s. They are sometimes long with the changes, notes, intent etc and sometimes short.


There's also Boon which I like quite a lot but I opted against using mostly because of all the places I would need to type where I wouldn't have access to Boon unless I ported it (a plan I assure you but one lumped behind 1,000 other projects TODO).

https://github.com/jyp/boon


Addressing just the capture: I don't see the problem with `||` at all, in-fact I think it's elegant. I do like (most of) Ruby's syntax so that's probably where my fondness of this comes from but I am not a veteran or seasoned Ruby expert by any means.



Thanks! Macroexpanded:

Show HN: Make 3D art in your browser using Lisp and math - https://news.ycombinator.com/item?id=32738654 - Sept 2022 (38 comments)

Janet – a Lisp-like functional, imperative programming language - https://news.ycombinator.com/item?id=28850861 - Oct 2021 (135 comments)

Janet Programming Language - https://news.ycombinator.com/item?id=28255116 - Aug 2021 (114 comments)

Janet: a lightweight, expressive and modern Lisp - https://news.ycombinator.com/item?id=23164614 - May 2020 (269 comments)

Janet – A dynamic language and bytecode VM - https://news.ycombinator.com/item?id=19179963 - Feb 2019 (50 comments)

Janet, a Clojure inspired language for scripting, or embedding in other programs - https://news.ycombinator.com/item?id=19172510 - Feb 2019 (1 comment)

Janet, a bytecode Lisp vm - https://news.ycombinator.com/item?id=18759277 - Dec 2018 (1 comment)


I don't know how I feel about this.

It is _technically_ cool but I feel like this existing is a definite step backwards with regards to Node.js' lack of modern web APIs.

Software like this relieves pressure in moving from Node.js specific APIs towards standardised web APIs and in addition to that itself boasts about portability by ignoring modern features too. From their WebContainer vs Nodebox FAQ:

    Nodebox runs on any browser because it was built from the ground up with cross-browser support in mind, avoiding modern features like SharedArrayBuffer."
Link: https://sandpack.codesandbox.io/docs/resources/faq#how-does-...

So now we've got an escape hatch for Node.js not having to implement modern APIs because software like this implements its runtime for the browser, and also this same software removes pressure on browser vendors bringing their implementations up to webstandard specifications by "... avoiding modern features".

While this is _technically_ cool I feel like it's a lose-lose for the overall ecosystem.


All specifications (with links to repos): https://solid.github.io/specification/

Solid protocol specification repo: https://github.com/solid/specification


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

Search: