HN user
That is a sharp and slightly chilling analogy. If Steve Jobs saw the computer as a tool that amplified human effort (the bicycle), and AI represents a tool that automates that effort entirely (the car), then the "obesity epidemic" of the mind is likely Cognitive Atrophy.
- Gemini
Ah, a new "WTF": Worse Than False!
Public sector? In my country working for the energy grid operator feels like a constructive and positive contribution.
Sorry about your dark place. Keep looking for the light!
Very interesting! Who made this?
The technique can be applied by any engine, not just DataFusion. Each engine would have to know about the indexes in order to make use of them, but the fallback to parquet standard defaults means that the data is still readable by all.
Watch out for fulings on the plains!
That transcription reads very much like a NotebookLM "podcast" summarising the actual article at https://www.scientificamerican.com/article/outrage-fatigue-i...
Hilbert curves are used in modern data lakehouse storage optimisation techniques, such as Databricks' "liquid clustering" [1]. This can replace the need for more traditional "hive-style" partitioning, in which the data files are partitioned based on a folder structure (e.g. `mydatafiles/YYYY/MM/DD/`).
I wanted to build a Windows container image but I really did not want to install Docker Desktop. After some digging around I found my way to the Docker server / client binaries for Windows page that allowed me to do this: https://docs.docker.com/engine/install/binaries/#install-ser...
Interactive LLM Powered NPCs, is an open-source project that completely transforms your interaction with non-player characters (NPCs) in any game!
Like Mastodon to Twitter? I like the idea, but it's not really taking off, is it?
Fabric does not use Databricks, but both Databricks and Fabric rely heavily on Delta. Let's just hope that they remain compatible.
This is interesting... possibly a move by Databricks to try and build on their "data lakehouse" concept to counter the recent "Fabric platform" announcements at MS Build.
Databricks coined the "Delta lake" concept and are still (just about) leading the way, but Fabric has the potential from MS to take away that marketshare. Databricks need to improve their "serverless SQL" offering, and add a serious "data warehouse" component alongside the lake.
Does it work with LocalAI [1] if you change the openai.api_base value to http://localhost:8080/ ?
No
Windows 11 is the perfect time to switch to Linux (especially for first-timers), using WSL2. Then, once you're familiar with Linux, it's a shorter jump to replace Windows completely (and appreciate how fast Linux can be without WSL)
"it ain't great, but it could be a lot worse..."
Oh, this has been submitted before, sorry!
Good work! Keep at it. You're not alone.
Exactly! We're never old, we're new, constantly. :)
TL;DR: no, because physics! :)
The operators we offer in our clusters (e.g. ECK, Prometheus, etc... the ArgoCD ApplicationSet generators make it easy to configure which features are installed on each cluster), as well as the applications developed by the development teams. Our work isn't complete yet (still working on sync for secrets and RBAC), but it's working nicely so far.
I like Terraform for infrastructure, up to the point of creating the K8s cluster, then ArgoCD for keeping K8s in sync.
That doesn't necessarily mean that the content is the problem. 200 years ago you could probably say the same thing about "basic algebra" instead of "serious physics".
Good point. Whatever the default is for a Samsung S10e. I agree that the forking by all the manufacturers is a PITA.
I had this one (by ZXing Team) and never noticed any negative behaviour, but given that the default camera app now supports QR Code scanning I don't see a reason to keep the Barcode Scanner app.
It's 2021, but I agree with the rest of your post :)
Not really (any less). A couple of years ago we migrated a project from Spring + GWT to Spring + Vue. The Vue part is nicer, but everything around it feels messy. The team is primarily backend / java developers (we had a frontend expert at the time too), but we felt that the JS frontend part shouldn't be that hard to master. Maybe Vaadin would have been a better option after all?