Search
1000 results for “data0”
-
All hardware is supported, there are no known bugs and you even get OTA updates once a month including the latest security patches from #Google. At 7 years old, it's still a perfectly usable daily driver.
But what about the #Teclast tablet? It got stuck on #Android5.1 right out of the gate, only receiving a few patch updates. And you can see why: It sports a rather esoteric #Intel #i686 (32-bit x86) SoC and being a very cheap device, it was not economically feasible to keep it updated.
[2/4]
-
All hardware is supported, there are no known bugs and you even get OTA updates once a month including the latest security patches from #Google. At 7 years old, it's still a perfectly usable daily driver.
But what about the #Teclast tablet? It got stuck on #Android5.1 right out of the gate, only receiving a few patch updates. And you can see why: It sports a rather esoteric #Intel #i686 (32-bit x86) SoC and being a very cheap device, it was not economically feasible to keep it updated.
[2/4]
-
All hardware is supported, there are no known bugs and you even get OTA updates once a month including the latest security patches from #Google. At 7 years old, it's still a perfectly usable daily driver.
But what about the #Teclast tablet? It got stuck on #Android5.1 right out of the gate, only receiving a few patch updates. And you can see why: It sports a rather esoteric #Intel #i686 (32-bit x86) SoC and being a very cheap device, it was not economically feasible to keep it updated.
[2/4]
-
All hardware is supported, there are no known bugs and you even get OTA updates once a month including the latest security patches from #Google. At 7 years old, it's still a perfectly usable daily driver.
But what about the #Teclast tablet? It got stuck on #Android5.1 right out of the gate, only receiving a few patch updates. And you can see why: It sports a rather esoteric #Intel #i686 (32-bit x86) SoC and being a very cheap device, it was not economically feasible to keep it updated.
[2/4]
-
This is such a good article, anyone (any real person anyway) doing open source should read it! 👏👏👏 @andrewnez
> #GitHub made #forking a one-click operation a decade ago without ever investing in making the resulting graph navigable […] A pull-based model would sidestep most of this, because #agents can #fork and generate garbage all day without anything landing in anyone’s inbox.
-
Probably a good time to repeat myself:
- Run your #node-based prod app **AND** dev stack in isolated #containers / #vms (most malware targets you, the dev!)
- Use as few external packages as possible
- Check all packages carefully before installing, incl. updates (grab tarball and use #diff when in doubt!)
- What you see in a module's #GitHub is not necessarily what's on #npmAnd btw, the issue lies with npm and the move-fast-and-break-things culture, not #javascript
-
I enjoyed this article on #vim #minimalism, even though it's a bit too extreme for my taste. I too try to keep my setup as lean and use as much built-in functionality as possible. But I still think syntax highlighting and LSPs are genuinely useful. #LSP feedback should be entirely on-demand of course. And compiling commits with #fugitive is just so much faster and more flexible than with the #git #cli. But apart from that… right on!
-
@seanhood You could try solving the #AdventOfCode with #VimScript ;-) Nah, better not. AoC should be about having fun.
-
-
It's #fork switching time!
#Rome is my favorite #JavaScript #linter and #formatter. It's easy to configure, super-fast and has superb editor Integration thanks to its built-in #LSP.
But it got burned down by VC money.
Fortunately though, the core team members have rescued it by creating a new fork: #Biome! Try it out! Happy to share my #NeoVim config.
-
@emmanueltouzery IMHO, #React has lost its way a bit lately by focusing too much on the #serverside and getting too entangled with #Nextjs. Maybe it was a requirement from Xeta, who knows. I still like the paradigms and APIs React introduced, but now prefer other libraries for interaction-heavy websites and SPAs.
-
-
#Ed25519 is now supported in all major #browsers. Big up @igalia!
-
Oh my <overlord of choice>…
"There is also an unfortunate #bug that is not fixed to this day that result in an excessive creation of .DS_Store file. Those files should only be created if the user actually makes adjustments to the […] folder. That’s unfortunately not what happens and visiting a folder pretty much guarantees that a .DS_Store file will get created"
On the origins of #DS_store
https://www.arno.org/on-the-origins-of-ds-store -
One of my favourite #feeds in my #RSS reader is #Wikipedia's "On this day..." #feed. It always includes something interesting to read and delivers several deep #rabbitholes per week. Highly recommended!
https://en.wikipedia.org/w/api.php?action=featuredfeed&feed=onthisday&feedformat=rss
-
I'm trying to track down a weird issue with using #streams as request body for #fetchapi requests in the #browser. After the first chunk is read, the connection stalls and the server never receives any data. It seems to be related to #http3 / #quic. When I downgrade the http reverse proxy to #http2, it works fine.
Has anyone experienced this too? Are streaming request bodies not compatible with http3? (as currently implemented in #chromium)
-
Same!
> I've always tended to be a web maximalist, but I've never felt more optimistic than I do now about the power of the modern web as a true application platform. @ameo
https://cprimozic.net/blog/building-a-signal-analyzer-with-modern-web-tech/
#Browser #WebDev #WebWorkers #SharedArrayBuffer #OffscreenCanvas #Wasm #WebGPU
-
@emmanueltouzery A year ago I took a risk and started building a big-ish app with #Preact where I would have otherwise used #React. So far it's going great. It also encouraged everyone to use much less external dependencies and build out more stuff themselves which in turn makes maintenance much easier and the whole app more future-proof. And it turned out the `compat` module needs to be used much less than originally thought.
-
@aoristdual I'd probably look for something that doesn't need another toolchain (i.e. compilation) to keep things as simple as possible. Using #preact as a native es module together with #htm to write #jsx-style template tags for example.
https://preactjs.com/guide/v10/getting-started/#alternatives-to-jsx
-
Oh no! This will lead to a massive #shortage of #Z80 #CPUs this year! We'll be hearing stories of mysterious break-ins where nothing more than a #Commodore #C128 was stolen from the basement game room. It's going to be terrible!
-
The #wasm build of #sqlite opens up great new possibilities in the #browser, especially when coupled with the Origin Private File System (#opfs). I've used it to implement importing huge #csv or #jsonl #datasets right in the browser. Import, validate, search, edit, close the browser and continue tomorrow, stream the database (with on-the-fly compression!) to the server when ready – it's all possible!
Another interesting use case I came across today: use it in #golang to get rid of #cgo!
[1/2]
-
Surprise, surprise! #youtube doesn't care what you like. It only cares what you'll watch next. And it's not the same.
-
Much of what #JohnSculley (then CEO of #Apple) predicted in 1987 became true.
> The problem is the growth of information […] So the ultimate aim of computers will not be to create more information. We need the ability to navigate in real time across vast expanses of information. […] Information is an interim step to the ultimate goal of knowledge.
https://fosstodon.org/@johnblood/113477048659947227
(1/3)
-
Unhappy with #DockerDesktop on #macOS? Give #Colima a try!
It's a free and open #container runtime for macOS. It now supports the macOS #virtualization framework, #virtiofs for fast volume mounts and forwarding #inotify events for hot/live reloading. It can even provide a #containerd, #kubernetes or #incus runtime.
https://github.com/abiosoft/colima
(I would've preferred #podman, as that's what I'm mostly using in production, but it still doesn't support forwarding inotify events on macOS)
-
Nice side effect: My config is now down to just a single file with 36 lines, 19 of which are folder name configs probably very specific to my users.
Conclusion: For as long as there's no #openimapd, #dovecot is still the preferred (read simplest) #imap server for little self-hosted setups like mine.
[3/3]
-
Two of the nicest new #JavaScript features of recent times:
Iterator Helpers (`.values()`) and `Array.fromAsync()`
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/fromAsync
-
This amazing, cursed, fun, terrifying, makes you sick if you've ever worked in #networking and incredibly entertaining all at the same time:
https://1.6.0.0.8.0.0.b.e.d.0.a.2.ip6.arpa/@domi/statuses/01JQHWXY605XVPGY5MAXV30K5X