- infamia parentF-Droid is no longer accepting "NSFW" apps (as they dubiously define them) and will eventually remove them from the repo. This tag is only a stopgap until they figure out how to move them out of the F-Droid repo.
- No, there are plenty of other examples (just in games alone) to write off as a mere one-off oversight. It certainly seems targeted since they've targeted religious apps that don't even have any explicit content. For an app store that is supposed to advocate for freedom this is disturbing and very off-putting. The answer is not submitting a PR to enable even more censorship.
- Gloomy Dungeons 2 is mentioned in the discussion as an FPS without the NSFW tag:
https://gitlab.com/fdroid/fdroiddata/-/merge_requests/27861#...
The NSFW tag seems unevenly enforced, especially for an organization that is supposed to oppose censorship.
- The data attributes they moved to Pro was mostly a result of watching folks use Datastar and seeing the anti-patterns develop. Those anti-patterns have been moved to Pro.
> If it's stable, no v2, plugins aren't needed, it's a 501c3, there's no shares, equity... what's the point of Pro? "The goal is to fund the work and draw a clear support boundary," What are they funding?
I assume it is because charitable organizations need accountants and other things (along with all the other stuff like web hosting and the like).
- Try Datastar, it leans into web components, and they're working on a plug-in that integrates web components with Datastar. For example, I believe the star field on the front page of it's site is a web component.
- > Highly disingenuous. First, AI being trained on copyrighted data is considered fair use because it transforms the underlying data rather than distribute it as is.
Your legal argument aside, they downloaded torrents and trained their AI on them. You can't get much more blatant than that.
- 1. Move the deductions from the employer to the individual. That unlinks health care from your employer. It will also inject market forces and discipline to our health care system, since the person paying for the care is now in charge of the insurance.
2. Repeal the ACA mandates and enact interstate laws which permits low-deductible, low mandate policies along with reintroducing catastrophic insurance. The current status quo forces young people to pay for old people and those less responsible with their health. What we have now is prepaid medical care, not insureance. This also removes the insurance monopolies states and companies have created together.
We have the worst of all possible systems at present.
- Using WAL2 should make that problem better. It has two WAL files it alternates between when making writes, so the system has an opportunity to check point the WAL file not in use.
- TLDR: Yes.
As of this release, No-GIL/free threading Python has moved out of the experimental phase and is officially supported in this release. No-GIL Python is not the default for this release (that's potentially the next phase of the project), but running no-GIL/free threading is officially blessed.
- > Pyright was released first and was and continues to be open source. Pylance was built on Pyright but has never been open source.
No, the first Python extension that shipped with vscode 1.0 in 2016 was called the "Microsoft Python Language Server" and was based on the Jedi LSP. Below is the deprecation announcement of the Jedi language server in the Pylance launch post below.
> In the short-term, you will still be able to use the Microsoft Python Language Server as your choice of language server when writing Python in Visual Studio Code. > Our long-term plan is to transition our Microsoft Python Language Server users over to Pylance and eventually deprecate and remove the old language server as a supported option. https://devblogs.microsoft.com/python/announcing-pylance-fas...
> But they are probably worried about Windsurf and Cursor, the latter of which (a billion-dollar company) was caught violating MS's TOS around the plugin ecosystem.
If that were so, I would certainly understand. However, MS started closing vscode and the extensions years before Windsurf and Cursor (initial release in 2023). This was their business model all along get adoption in partly by leveraging the open source community, and then close things off slowly once they have a choke hold (similar to Android/AOSP). I could scarcely agree more that Windserf and Cursor are supremely sketchy and generally scummy companies.
Consider MS launch announcement that focuses on open source, extensibility, open community, and a promise to be transparent with their intentions (i.e., vision) and roadmap...
> From the beginning, we’ve striven to be as open as possible in our roadmap and vision for VS Code, and in November, we took that a step further by open-sourcing VS Code and adding the ability for anyone to make it better through submitting issues and feedback, making pull requests, or creating extensions.
https://code.visualstudio.com/blogs/2016/04/14/vscode-1.0/#_...
Except they weren't open and did a u-turn on the community a few years later. MS started closing sources and locked things down a few years later despite touting the benefits of being open and open source in the announcement above. Now they have architected the Python extension so it only runs on vscode, and will not run at all on any fork, which is pretty shady after promising transparency and openness.
- > Their existing and continued contributions to vscode are significant, so I think they can be allowed to keep some cards up their sleeves like the plugin marketplace or their Python extension.
It would have been fine if MS had started with their Python extension being proprietary, that would have been up front and transparent. Instead, they lured folks in (no small part due to open source), and once it became popular, they started turning the screws and making things proprietary and locking it down.
> I'm just flabbergasted at this idea that somehow we're entitled to everything vscode-adjacent "just because"
You're not arguing in good faith at this point. I don't think it is unreasonable to ask someone to make their intentions known up front do you? Instead MS waited until vscode became popular (partly because everything was open source) and then altering the deal Vader style closing off parts of vscode and extensions that were open. That doesn't feel particularly transparent.
> or that Microsoft is obligated to subsidize other billion-dollar business by giving them free features for their vscode forks.
I have no idea what you're talking about here. Vscodium is an entirely free and open source fork, no one makes any money from it afaik.
> Where's the bait? Where's the switch? If the best you have is that they released a closed source plugin I'm going to bucket this as another borrowed opinion.
They released the Python stack as fully open source. Then released the proprietary one, deprecating the open source one. Then made double certain that vscodium or any of the other forks could not use it at all, even if the use manually downloaded the extension. How is that not a bait and switch?
- VSCode's marketing was that it is an open source editor you could rely upon, complete with open source extensions for popular languages like Python. Then when once it became popular and vscodium was growing in popularity (a vscode fork), MS locked things down. Now the Python extensions are closed source, and MS has artificially prevented vscode forks from using those extensions. A bait and switch if I've ever seen one.
- idk if I'd put it quite that strongly. https://data-star.dev/examples/dbmon
Also, multiplayer for free on every page due to SSE (if you want it).
- You can use uv to pin, download, and use a specific version of a Python interpreter on a per project basis. You shouldn't use your OS provided Python interpreter for long running projects for all the reasons you mentioned, including reproducibility. If you insist on using the vendor provided interpreter, then use RHEL (or a free clone) or any other long suppported Linux distro (there are many). Five years is a very long time in technology. It is not reasonable to expect more from core maintainers IMO. Especially considering we have better options.
- > No, it is not. There's no way to send the incremental results of typing in a search box, for instance, to the server with HTML alone - you need to use Javascript.
Hypermedia applications use javascript (e.g., htmx - the original subject), so I'm not sure why you're hung up on that.
> And then you're still paying the latency penalty, because you don't know what the user's full search term is going to be until they press enter, and any autocomplete is going to have to make a full round trip with each incremental keystroke.
You just send the request on keydown. It's going to take about ~50-75ms or so for your user's finger to traverse into the up position. Considering anything under ~100-150ms feels instantaneous, that's plenty of time to return a response.
> As someone building web applications - no, they really aren't.
We were originally talking about "normal" (js) web applications (e.g. react, angular, etc.)., most of these apps have all the traits I mentioned earlier. We all have used these pigs that take forever on first load, cause high cpu utilization, and are often janky.
> My webapps sip power and compute and are low-latency while still being very poorly optimized.
And now you have subtlely moved the goals posts to only consider the web apps you're building, in place of "normal" js webapps you originally compared against htmx. I saw you do the same thing in another thread on this story. I have no further interest in engaging in that sort of discussion.
- > This is factually incorrect. Latency is limited by the speed of light and the user's internet connection.
This is a solved problem. It is simple to download content shortly before it is very likely to be needed using plain old HTML. Additionally, all major hypermedia frameworks have mechanisms to download a link on mousedown or when you hover over a link for a specified time.
> If you read one of the links that I'd posted, you'd also know that a lot of users have very bad internet connection.
Your links mortally wounds your argument for js frameworks, because poor latency is linked strongly with poor download speeds. The second link also has screen fulls of text slamming sites who make users download 10-20MBs of data (i.e. the normal js front ends). Additionally, devices in the parts of the world the article mentions, devices are going to be slower and access to power less consistent, all of which are huge marks against client side processing vs. SSR.
- > Unfortunately, that means that the tradeoff is that you're optimizing for user experience instead of developer experience
Not really, your backend has rich domain logic you can leverage to provide users with as much data as possible, while providing comparable levels of interactivity. Pushing as much logic (i.e., state) while you're developing results in a pale imitation of that domain logic on the front end, leading to a greatly diminished user experience.
- Regarding #3, you can already do this with Jinja2 template functions perfectly well. You can also do it with template tags, but it isnt as nice.
100% agree with #5, the diaspora of Django's community, dev process, and lack of a single decision maker when consensus isn't quickly reached, makes it virtually impossible to correct past mistakes.
- > Multiple readers are okay but a single writer will cause transient errors in all other concurrent read and write operations
While in WAL mode, readers and writers don't block one another.
> WAL provides more concurrency as readers do not block writers and a writer does not block readers. Reading and writing can proceed concurrently. https://www.sqlite.org/wal.html
- > I don't know about you, but I am much better at decoding separate RGB values (as in, including hex) than I am at decoding a single chroma value.
I can do it, but RGB and HEX are awful for me. A lot of mental work must be done to get to decimal/hex colors:
1. Memorize what happens when you mix combinations of RGB.
2. Learn/internalize hex
3. Mentally map how each color might roughly look in both decimal and hex.
All of that can be learned of course, but that's a lot of work compared to memorizing four numeric waypoints for hues (Red, Yellow, Blue, Green) to start. The rest was super easy for me once I knew that Chroma is how much color you're putting in (0=gray). By the way, you mentioned Chroma earlier. Did you mean Hue instead?
The beauty of OKLCH is that you don't absolutely have to know Hue cold to work with colors and create variations. You can pick your primary, secondary, etc. colors. Then set the Chroma (which probably remains the same throughout your palette) and Hue to CSS variables. Then forget about their real values and just use the variables. To get a color palette, adjust with the brightness to develop as many levels of a color as needed. Then, take that color and copy/paste for however many colors you have in your palette, replacing the hue with a different variable for each color. All the colors will have the same perceived brightness at a given level of lightness, which is a huge win that isn't easily achieved in other color systems like RGB.
- I hear ya, but it is CSS so the target doesn't move, Codeberg is using it for their docs [1], and it is easy enough to paper over any problems you might find. Good enough for me. Some might even say the more relaxed release cadence is a feature not a bug.
[1] https://github.com/halfmoonui/halfmoon/issues/116#issuecomme...