Necuvioșia este legătura incorectă cu Dumnezeu sau deplina uitare de Dumnezeu https://bit.ly/47KvHnA #binecuvântarealuiDumnezeu #bun #Cădere #conştiinţă #credinţă #CuvinteDuhovniceşti #deplinauitare #Dumnezeu #existența #gandnecuvios #legaturaincorecta #necredință #Necuviosie #SfântulTeofanZăvorâtul #suflet #TâlcuiridinSfântaScriptură #Zidire
1... 2... 3... 4... ... ...8... 9...
When one egg makes room inside, there's always that feeling you could just get that... one... more... in... and another. The pressure vying for release as they settle inside that warm space~
Just one more...
super surprise eggs from asralore , thanks so much!
The clutch was ready, they had incubated well, and with that familiar pressure - it was time. Time to let the slimes have their eggs.
Absolutely awesome gift from Bedethingy, thanks again!
The hype train already stopped after the honeymoon phase is over.
See also: https://dev.to/thejaredwilcurt/bun-hype-how-we-learned-nothing-from-yarn-2n3j
Long post but pretty important if you want to make a prober decision.
So I've been doing some experiments to switch internal #ThingUmbrella tooling to https://bun.sh. The _much_ improved launch time per process could quickly save me a _ton_ of time when repeatedly batch processing 185 packages (be it for building, readme & doc generation/updating, releasing etc.)...
The main thing holding me back from making the switch already is `bun` offering only partial support for #Windows. I'm not a Win user myself, but don't want to exclude (or make it harder for) Windows-based contributors ("normal" users wouldn't be impacted by that change)...
Thoughts? Anyone else in a similar boat?
If JS had checked exceptions, that would make it very convincing as a suitable Go replacement for my work.
It’s crazy fast which I love, but the bundler keeps changing class names. Build does the same. Not exactly great for a JS library.
So all that effort and I’m still on webpack & npm. But I cleared out some other issues.
[TUTORIAL] Imparare Bun, un'alternativa più veloce a Node.js
> You can't get faster than No Build
#bun 1.0.4 performance is impressive.
They are clocking at about one new issue per hour.
Gave a try on #bun.sh at work on our (quite complex) software. Performance seems great, but bun.sh is not an option at the moment because it seems to be not (yet) able to install package.json requirements from github repositories.
Anyone perhaps knows if and when that support is planned? I can't find anything about this topic.
♦️Ruby more your thing? https://git.jmes.tech/james/ruby)
❓What is this weird git website? I run my own code forge on a little VPS now. Using Forgejo.
@deadparrot @brianleroux thanks for sharing the article about the hype around #bun. Guess the backlash is basically a healthy dose of skepticism, in the face of blind optimism. Seeing people jump ship after some hello world #benchmarks.. actually tells me that the next generation again appreciates computing and power efficiency. That is an invaluable change in attitude. (But it’d make more sense if they switched to coding in #Zig themselves)
Oof, so #Bun doesn't support #NextJS yet (or at least the App router which I am using, plus some experimental features), so I have to keep running it with #NodeJS. I'm also installing sharp which is a native module, and it doesn't seem to work if I install it with bun but run with npm, which makes sense.
But now have to install, build, and run with node. I can only use Bun to replace ts-node. Which is something but pretty underwhelming for now.
Un peu de nuances sur tous les superlatifs employés pour la promotion de Bun, l'alternative vendue comme extrêmement performante à Node.js.
My thoughts on Bun and other Adventures
All the ESM/CommonJS issues I've been dealing with are gone. #esbuild? Don't need it anymore. The weird dev reload thing I taped together with chokidar, #TSNode, and npm-run-all? Nope, bun --watch is all I need now.
If you haven't, give bun a chance at least.
This is actually a pretty awesome (but lengthy) post about Bun and why you probably shouldn't jump on the train already.
Bun hype. How we learned nothing from Yarn
Also I hope they are careful and do not introduce only bun compatible into lodash itself, but I think they hopefully know what they are doing
I still would have preferred a fork-rewrite instead of this atombombing strategy
That said it is not about me.
See the recent project 'bun', all-in-one nodejs replacement which solves many problems.
Unfortunately for them they chose Zig for reasons that are not entirely clear to me.
Had they chosen Rust - a clear use case - it would have been a huge boon instead of being security hot mess.
...I think I hadn't painted my nails in around a year😳 And gosh, now that I've done it, it makes me feel really well put together all of a sudden🤣
...a welcome change after a month of feeling like shit "thanks to" bc side effects😮💨
The company behind it is really into grind culture. That's such a turn-off, I don't even care if the product's any good or not. I don't want to promote developers (or *anyone*) having to grind really hard, and I want people who do promote that idea to go out of business.
The TL;DR is I broke everything while upgrading libraries and modernizing the #LDJam software stack, but thanks to #ESBuild and #Bun, our #JS and #CSS build times are 1 SECOND now instead of several minutes... not to mention live IDE linting, #TypeScript support, and live reloading. 🤯
I'm hoping to deploy tomorrow.
I've switched out npm/yarn for Bun just to try it out.
`npm run` => `bun run`
`npm install` => `bun install`
...and, everything works? I'm trying it so far on some Astro sites expecting things to break, but... it's so seamless.
Honestly blown away by #bun's goal of Node.js compatibility.
after several attempts at testing it, my conclusion is that #bun is overhyped and rushed to ‘release’ software of alpha quality
I see no applications where I want to use it, even its own tools aren't working. trading stability for performance is probably the worst trade you can make
and I have suspicions about the intents behind deno and bun. like I just don't have any good feeling about VC funded business like that
Bun does some interesting things. But being the VC-funded product that it is, it will soon push Oven's commercial products (cloud hosting) ever more aggressively and try to lock users in. #Deno is VC-backed too, btw. #Node on the other hand is a real community project and making good progress lately.
Wasn't that #Bun? Or am I misremembering? I wanted to never use whatever-software-it-was. I feel bad about not remembering.
🥟 Bun 1.0
Is Bun the future of JS Runtime?
1. Blazing fast.
2. Transpiler: Typescript support out of the box.
3. Package Manager: No npm requirement, Bun is a package manager.
4. Bundler: Is a bundler like webpack.
6. Test Runner: Has a test runner built in that is compatible with Jest.
7. Resolves both CommonJS & ES Modules so devs dont have to deal with it.
Check out the changelog, there are a couple of minor breaking changes:
And if you have a Deno project you've been wanting to use SimpleWebAuthn with (without having to resort to
npm: specifiers) you can find the project on deno.land here:
Time to rest 😮💨
⚡️ New episode of JS Party! ⚡️