It's not only an awesome technical achievement, but it has also so much potential to be useful.
And yet, something at the back on my head is screaming:
WARNING!
I have the intuition that, on the long run, using more and more tools that are not on your own machine will create a dependency on systems big companies control. And something tells me we are going to pay for it in the end.
So I'll stay away.
Maybe I'm getting paranoid, but I don't regret not having ever created a Facebook account, or not getting on the 2010 hype train of magical SAAS services like Firebase that lock you in eventually.
This is my personal opinion. I don't imply in any way or form that my point of view is right. You can down-vote, call me names, or ignore what I am sharing. I don't care.
Since Apple CSAM attempt, something at the back of my head screamed: Regroup. React. Change. Now.
Two months after Apple's "postponing for better implementation": My company runs on Arch/Manjaro (over old MacBooks Pro without T chip, custom PC's, etc). There is no iPhone in sight - my colleagues/employees found personal alternatives. I use DeGoogled Android device for banking app and flip phone.
Designers are with powerful Linux boxes: Windows VM - mainly Figma (I don't like it, but this is production standard now) and Affinity Designer/Photo.
We use mainly Vim/Emacs/VSCodium/Sublime.
Vendor lock-in is inevitable, SaaS business logic is based on this premise. I don't care how cool it is, or how 'trendy', there is no way my company production code to be served as a "free petrol" for some monopolistic/"good intention" scheme which will feed AI advancements geared towards removing of skilled professionals.
I don't like SaaS apps direction at all.
We have powerful hardware now, there are proven ways of collaboration with FOSS, moving everything in the browser is utterly insane.
I cannot hide how I feel about the lack of critical thinking in designers and developers today.
They are always ready to jump on the bandwagon just to feel 'cool and important'.
Call me crazy, or paranoid. In 5 years time all will be transparent and obvious even for the most "optimistic" ones.
We are back at UNIX/VMS/mainframe timesharing infrastructure.
SaaS direction is the only way people have found out to extract money from open source tooling that devs don't want to pay for, it is either SaaS or hardware, so there you have it.
> We are back at UNIX/VMS/mainframe timesharing infrastructure.
It is worst. We are in the new times of "surveillance economy", "data hoarding", politically driven business decision making, 4th industrial revolution, real-time data driven "psyops" and "marketing", "AI advancements", you will own nothing and you will be happy.
I will gladly return to UNIX/VMS times with low connectivity, real human connections and minimal dark patterns in design and product implementation:)
It's already that way. It's immensely hard to "develop on an airplane / desert island". eg: even documentation is at best something like "dash" => https://kapeli.com/dash ... forget about anything more complicated than SQLite, and if you're lucky docker-compose for occasionally connected use.
My experience? Chromebook / Crouton, usually offline with occasional network access. I ended up leaning hard towards SPA's + javascript, with most of the documentation being "legit" available. (JS, HTML, CSS, DOM, etc.) ...occasionally researching + pulling in libraries on occasion.
This is running on your machine though. The browser downloads vscode as a SPA-style thing, and runs the editor in the browser sandbox, and can edit local files/directories.
Sure. And the google map api is free to use, you can send tweet using sms, facebook doesn't show ads and web services never change policies once they get enough users.
Good thing it's running on your machine and you can see and control when it updates.
My way to work around this is to make a zipapp that contains several files, hence the entry point can do the checking and import another file that contains the code. But since its a zipapp, it behaves like a single file script: https://docs.python.org/3/library/zipapp.html
Yes, by paying for things and people. Because that's more valuable than paying taxes.
However, that only works if one's willing to forego paying shareholders dividends (which are paid out of net). Lots of people are not willing to do that.
> Was that paragraph meant to be clickable or extendable?
The next four sections expand on it: see what apps are using the mic and camera, option to give apps only approximate location data, app permissions dashboard, and the local computation for some data.
True, though one may turn that around to say Cue's scope is too large while Jsonnet's is more "pure" while still enabling the larger scope.
Schema that describes data is itself just data and Jsonnet can describe both. While the various Jsonnet compilers do not "know" about any specific meta-schema in which to express schema nor of course any way to apply that schema to data for validation, one can create such systems with Jsonnet as the language and its compilers as a component.
True, CUE has quite the inspirational scope right in the name. It is actually what draws me to the language. I also like the theoretical foundations in being turing-incomplete. Functions and computation make configuration harder to understand and reason about.
I mostly generate yaml and json now that I've been using CUE. The cool thing about CUE is that it's really doing both at the same time. Types and values are just points along a spectrum of specificity, going from types to constraints to concrete values.
I found CUE because I needed something better than Yaml for generating code, or declarative application code. (https://github.com/hofstadter-io/hof). It was similar to when I found Go and replaced a bunch of C++. I gained way more functionality in my application while shedding more than 50% of my LOC.
Not OP, but "parse, don't validate"[0] says that data (including config, etc.) should go through a "parsing step" (no "shotgun parsing"[1]) which outputs specific data-types for the main processing code to deal with ("invalid states should be unrepresentable"[2]).
For example, we might have a "parsing step" which takes in Bytes (e.g. '[{"email": "[email protected]"}]') and outputs a 'NonEmptyList[ContactDetails]' (e.g. 'NonEmptyList(Email(NonEmptyString('c', "hris"), NonEmptyString('e', "xample.com")), Nil)').
Compare this to a "validate" approach, e.g. parsing the bytes to a 'JsonArray', and using a boolean function to check whether it's empty, and whether its entries match the 'contact details' schema. That's problematic, since (a) it leads to "boolean blindness"[3] (the function tells us 'attempting to get those fields should work', whereas the parsing approach actually gives us those fields) and (b) such a boolean function is actually redundant, since deleting all of its call sites (or forgetting to write them to begin with) would give us a program that still compiles and runs (whereas the parsing approach would give a type error: 'Given JsonArray, expected NonEmptyList[ContactDetails]').
CUE's approach seems to be similar to passing JSON values around, and occasionally performing validation checks (if we remeber to); i.e. validating, not parsing.
And yet, something at the back on my head is screaming:
WARNING!
I have the intuition that, on the long run, using more and more tools that are not on your own machine will create a dependency on systems big companies control. And something tells me we are going to pay for it in the end.
So I'll stay away.
Maybe I'm getting paranoid, but I don't regret not having ever created a Facebook account, or not getting on the 2010 hype train of magical SAAS services like Firebase that lock you in eventually.
We'll see in 10 years I guess.