Look at the Wikipedia page, it's a mix of open source and proprietary copmonents. The OS project describes itself on https://sailfishos.org/info/ as "open source based" rather than "open source". It seems they have opened up some stuff since the last time I looked, but as far as I can tell the Silica UI is still proprietary. See for example https://forum.sailfishos.org/t/silica-components-license-and...
Yes.
Not interested in putting them in the cloud in the slightest.
99% of what's on my desktop i don't want/need on my phone, work or whatever.
People misusing tabs for bookmarks need to get their head checked.
Surely the only way you find anything is in the address bar anyway, an there they are equivalent.
It's like using Chromium or whatever clone-a-chrome is hip at the moment. That does absolutely nothing to disrupt the status quo and is very much at the whim of the upstream "owner" whether you want to see it or not.
Disrupting the status-quo is important, but having a working communication device is more important to me. If AOSP is further along towards a working phone then I don't see why we shouldn't focus development efforts on it.
It only benefits the open source market in the long run because a working device will garner wider adoption.
If Payload is a framework or not is debatable. I think it's more like a data layer around a database for a any js app and an Admin Panel (that uses Next.js now). It might be called a framework for your own Headless CMS, because it is code first. So you basically code the panel and the data structure yourself.
React hasn't been a library since they added hooks.
Hooks themselves are just a solution to async code, but the implication was that react was no longer a state-based UI rendering library and became a full blown frontend framework.
Routing is only important for a single page applications. Frontend frameworks are applicable to normal websites as well, they don't have to be SPAs with routing, caching, etc.
From what you posted in this thread, I can tell with confidence you don't know shit about web development
Hooks solution to async code? Hooks make React full blown forntend framework? Routing only important for single page applications? Yellow gorilla bread butter? Chickity dickity web frontend back single page I understand much
React was a library before hooks. Now it is a framework and decides when your code runs, not you. And now it is a terrible framework with server components.
I think server components have been very badly marketed. They're totally opt-in, so I don't see how this would make React instantly a terrible framework. I for one think they represent a lot of value.
If you don't use them, then React is quite literally no different to you.
Javascript has a compiler called Babel, which plays a huge role in modern web development. It is in fact a transcompiler, meaning it doesn't turn your javascript into bytecode, it is just transpiling stuff without changing the level of abstraction.
React Compiler is just a babel plugin for automatic performance improvement, memoization specifically, for never perfectly memoized React code.
Can library have compiler? Well why can't it? For example stdlib has a compiler, because C does.
Nothing in that is actually doing what a compiler does above and beyond what babel, swc and esbuild are capable of.
What they've added is wrapping your code in more memoization functions, basically. All stuff that doesn't fundamentally transform the code, aside from inserting more `useMemo` and the like.
The JSX macro - which is itself already optional but everyone uses it - is just that, a handy macro with implementations available in every common bundler and transpiler out there.
"Framework" isn't really the best term for them to actually use to describe Payload. Its basically a tool for NextJS developers to quickly build a custom CMS. I'd think of it more like CMS-in-code than a framework.
RSC was marked stable in Mid 2022 and this major change is still in the process of unfolding through the ecosystem, because of course these things take time. And even though react might be the future, I have a hard time understanding a client side framework that currently becomes more of a server side framework being stable.
By that standard, nothing is stable. New features are added to HTML, the Linux kernel, x86, PHP, etc all the time. In fact, building on top of higher level abstractions can sometime insulate your application from this change too.
When i have joined a new project, i have asked for a "safari" from one or a few senior people. Show me "the big five" of your area. Pretty simple to find time and willingness for generally, and it's been a good amount of info to digest at once.
What is it with people and not understanding percentages?
"How Much Less Do Techies Get Paid Outside the Bay?"
"SF Bay Area 100%"
"Miami -88%"
So people in Miami are paying to work?
And even if it was meant to be relative to a baseline (which is not what it says!); i have a very hard time believing that they get only 12% the pay in Miami compared to SF.
Yeah, this was completely my bad. Any chance you'd like to proof future posts for stupid mistakes like this? :P I joke, but I'm writing 2-4k words per week, and the sheer number of simple arithmetic calculations makes it tough to catch even big mistakes.
Seriously, though, if you know of a way to proof posts (services, forums, etc), I'd be interested. What I need is an editor as a service. The blog is just a hobby, so I can't afford a real professional editor.
> Wow. Just wow. Is there really a mistake this big here?
Yup TFA is misleading and arguably plain incorrect.
If you make $200K in L.A. and $300K in SV, you need to use seriously creative math to deduce that: "How Much Less Do Techies Get Paid Outside the Bay? -50%".
Literally TFA says you're paid "minus 50% less".
Negatives (in both sentences and numbers) are a bitch, especially when there are two negatives or more.
TFA should say "How much more would you get paid by moving to The Bay?" and not use negative percentage.
(raw median)
"How much more would a L.A. dev ($200K) make by moving to The Bay ($300K)? 50% more"
The fault goes deeper; they say X percent less counted in percentage points of the compared thing and not the baseline. If you then have multiple rows, the uselessness becomes evident.
Is it some cultural or linguistical thing where it always has to be X amount more or less and never "Y% of"?
