Jet Set Radio OST: Guitar Vader - Super Brothers
#jsr
0 posts0 participants0 posts today
Continued thread
I'm definitely having fun hacking away at #silverbullet. 
Right now, getting used to using the #javascript import. Which can effectively pull almost any js module. And with #jsr being a thing... let's just say silverbullet instance is going to get weird. 
I'm honestly surprised it took this log to learn of this gem. Likely due to my still very much liking #logseq. Although... give me a few weeks... I'll likely build my own journaling system on this thing. 
silverbullet.mdAPI/jsAPI docs for Space Lua's js module, which provides JavaScript interoperability. js.import(url)Imports a JavaScript module from a URL. Returns the imported module.Example:-- Import lodash librarylocal lodashLib = js.import("https://esm.sh/lodash@4.17.
Resonac Holdings is studying deal structures for a possible acquisition of government-owned chip linchpin JSR. https://www.japantimes.co.jp/business/2025/02/19/companies/resonac-chipmaker-acquisition/?utm_medium=Social&utm_source=mastodon #business #companies #resonac #jsr #jic #chipmakers #acquisitions #ai
The Japan Times · Resonac explores deal structures for possible JSR takeover
I don't want to publish to #NPM because that organization has been shitty for a decade now.
#JSR seems like more of the same.
Why didn't #HTTP based #ESM #packageManagement catch on? #JSR says it's because you can't do #semvar, but I don't see why not; just use file paths ("example.com/package/major/minor/patch/")
I don't see an advantage to publishing #modules to a #package #registry at this time.
"I should publish a package to #JSR to see what it's like" ~ deranged nerd on the weekend
Thought it might be fun to make a small jsr package that actually has a bit of real-world utility. So here's `isit` as in `isit("Friday") ? "Hooray!" : "Boo!"` which I'll use in our morning work standup bot to send a different Teams meeting link depending on what day it is. Maybe it'll be useful to someone else too. It supports custom Dates and timezone offsets too. Enjoy! https://jsr.io/@phocks/isit
JSR@phocks/isit - JSR@phocks/isit on JSR: isit("Friday") ? "Hooray!" : "Boo!"
Just for fun I decided to try publishing a package on this new JSR "open-source package registry". Quick, simple, and fun. Love it! https://jsr.io/@phocks
jsr.io@phocks - JSR@phocks on JSR
> I’ve been noticing a trend with #DenoLand Inc. products. Engagement with users is fleeting. What I mean is that many reported issues with #Deno products are never addressed. Often they’re not even acknowledged. From #DenoKV architecture, to #DenoDeploy startup times, I keep running into show stopping issues with little to suggest they’ll ever be fixed. It’s not a good look.
dbushell.comJSR and Deno: Final Review 🚮The one where I am left wondering, why?
> #Deno has taken a U-turn on #HTTPimports and #JSR does NOT allow them. JSR allows node:, npm:, and jsr: imports, but not http:.
>This is a big deal because every single pre-JSR Deno #package with dependencies used HTTP imports. That was the Deno way. Those #packages are now blocked from publishing on JSR until upstream packages do — if they do. Few are. Curiously, for an immutable registry, the package count is dropping.
dbushell.comJSR and Deno: Final Review 🚮The one where I am left wondering, why?
Replied in thread
@baldur This is the kind of stuff #npm enables, right now in 2024:
https://blog.phylum.io/the-great-npm-garbage-patch/
The example of "axios" being cited as a dep of the package on the npm website even though it's really not is precisely the thing that #JSR is trying to counter.
Flawed and corporate, fine. But they're tackling a real problem here.
Phylum · The Great npm Garbage PatchHeaded to Black Hat USA? Come talk to us in Start-Up City at SC203!
In April of this year, the Phylum Research Team revealed the proliferation of spam packages in npm associated with the Tea protocol, a decentralized initiative that promises to compensate software developers in cryptocurrency for their open-source
Replied in thread
Deno BlogThe stabilization process of the Standard Library has begunThe Deno Standard Library is going to reach 1.0.0 shortly. We hope you try RC versions of the packages and give us feedback!
> JSR motivates best practices in code distribution—higher scores are awarded to packages that include comprehensive JSDoc documentation on each exported symbol
Replied in thread
@baldur FWIW the #Deno team has stated that they wanted #JSR to be a public utility for the JavaScript ecosystem and they’re still working out the particulars of how to govern the project.
https://deno.com/blog/jsr_open_beta
Considering that Isaac Schluter is in a new VC-backed company doing something similar, I think I’ll at least give #Deno and #JSR MORE of the benefit of the doubt based purely on what they have demonstrated so far. Hope they don’t prove me wrong. 
Deno BlogIntroducing JSR - the JavaScript RegistryThe JavaScript Registry (JSR) is a TypeScript-first, ESM-only module registry designed for the entire JavaScript ecosystem. Use JSR modules from Deno and npm-based projects. JSR is free and open source. Available today in public beta.
Deno boosts dependency management with JSR | InfoWorld 
https://www.infoworld.com/article/3714687/deno-boosts-dependency-management-with-jsr.html#tk.rss_all #Deno #JSR
InfoWorldDeno boosts dependency management with JSRDeno 1.42 brings faster startups, improved Node compatibility, and support for a new open-source package registry designed for TypeScript.
The CEO who drove a $7 billion deal is eyeing chip linchpin JSR as he pushes for consolidation within Japan's fragmented chip materials sector. https://www.japantimes.co.jp/business/2024/01/15/companies/japan-chemicals-maker-resonac-chip-investment/?utm_content=buffer58394&utm_medium=social&utm_source=mastodon&utm_campaign=bffmstdn #business #companies #resonac #hidehitotakahashi #jsr #chipmakers
The Japan Times · CEO who drove $7 billion deal is eyeing Japan chip linchpin JSR