5,684 karma · joined November 8, 2011
SPAs need to hold onto the data themselves, and correctly transition it between pages/components. Poorly-built ones will simply refresh it every time, or discard it if the data is too large.
Both mechanisms can allow for immediate page loads if they've been correctly implemented. They just require a different approach.
https://www.reddit.com/r/selfhosted/comments/1kgytl4/i_built...
Most of the time though, it just got in the way. I'd press tab to indent a line, and it'd instead jump half-way down the file to delete some random code instead. On more than one occasion I'd by typing happily, and I'd see it had gone off and completely mangled some unrelated section without my noticing. I felt like I needed to be extremely attentive when reviewing commits to make sure nothing was astray.
Most of its suggestions seemed hyper-fixated on changing my indent levels, adding braces where they weren't supposed to go, or deleting random comments. I also found it broke common shortcuts, like tab (as above), and ctrl+delete.
The editor experience also felt visually very noisy. It was constantly popping up overlays, highlighting things, and generally distracting me while I was trying to write code. I really wished for a "please shut up" button.
The chat feature also seemed iffy. It was actually able to identify one bug for me, though many of the times I'd ask it to investigate something, it'd get stuck scanning through files endlessly until it just terminated the task with no output. I was using the unlimited GPT-4.1 model, so maybe I needed to switch to a model with more context length? I would have expected some kind of error, at least.
So I don't know. Is anyone else having this experience with Windsurf? Am I just "holding it wrong"? I see people being pretty impressed with this and Cursor, but it hasn't clicked for me yet. How do you get it to behave right?
<link rel="alternate" type="application/rss+xml" title="fastcall's Blog" href="/index.xml">Some third-party tools exist to tweak how ClearType works, like MacType[1] or Better ClearType Tuner[2]. Unfortunately, these tools don't work in Chrome/electron, which seems to implement its own font rendering. Reading this, I guess that's through FreeType.
I hope that as new panel technologies start becoming more prevalent, that somebody takes the initiative to help define a standard for communicating subpixel layouts from displays to the graphics layer, which text (or graphics) rendering engines can then make use of to improve type hinting. I do see some efforts in that area from Blur Busters[3] (the UFO Test guy), but still not much recognition from vendors.
Note I'm still learning about this topic, so please let me know if I'm mistaken about any points here.
[1] https://github.com/snowie2000/mactype
https://drafts.csswg.org/css-mixins-1/
I do think it's strange that using a wrapper like var() wasn't required here. Like func() or such. I'd actually rather that var() hadn't existed to begin with, but it should be consistent, at least.
There was Google Contributor[1], which they tried three launching three different times before giving up on it. It seems like nobody was interested in paying to remove ads on the web.
I'd definitely consider this as being "available on F-Droid".
- Maintenance of roadways and bridges - Governments don't create wear and tear, vehicles and weather do.
- Food safety standards - Governments aren't harvesting lettuce with e. coli or selling diseased meat.
- Public healthcare - Governments don't create disease, but they ensure access to healthcare (at least the good ones do).
- Building codes - Governments rarely build houses themselves, but they do enact requirements for acceptable building materials, wiring standards, safe insulations, and so on.
- Environmental regulation - It's not entirely accurate to say that governments create zero pollution, but it's an insignificant factor compared to the industries for which they control regulations.
I'm sure some could try to argue each of these points with very narrow counter-examples, or try to stretch the meaning of "have a hand in creating" to be so wide as to encompass everything. Governments are a major part of society, after all. But on the whole, these are solutions created in response to problems in society that emerged naturally, without government oversight, programs, or committees behind them.
It's the same way on the desktop side. Writing everything in assembly instructions would technically be the least "complex", but it'd also be utterly insane and error-prone to do it that way. Even mid-level abstractions like C++ are hard to get right. It's why many modern apps are built in higher-level abstractions, because they're easier, more reliable, and fast enough.
It's really no different for a website. You can put all of your state in one place, bridge different libraries, and manually sync DOM changes, but you're essentially just frontloading the complexity. Abstraction is an important concept in structuring your codebase into clean and maintainable code, even if it is technically more complex.
I won't argue that React doesn't get overused for otherwise-simple pages, but many pages are not simple. The web today is full of interactions, tabs, dropdowns, search bars, notifications, modals, and tooltips. It all needs to respond to your device's form factor and input method. Every network request requires error handling. It needs to be routed, cached, and served smoothly and correctly.
It's a lot. It's a lot to manage in one layer. I am content to let some of that complexity be managed by Vue, or React, or whichever framework we're discussing. If it lets me worry just about my application's logic, and it simplifies the templating, error handling, routing, and so on, that makes things easier and less error-prone for me.
Honestly, I've written plenty of web apps in vanilla JS. I've experimented enough with closures, IIFEs, classes, and other techniques for managing state. It really doesn't matter how careful you are, any sufficiently-complex project will always turn into spaghetti. Frameworks help us stave that off, at least for a little while. Their component-based architecture makes relationships more explicit, and much easier to isolate. I particularly like Vue's Single-File Component (SFC) concept which organizes components into logic, template, and styling.
Not all frameworks require a build system though, and there's plenty of options available for tackling smaller problems. Alpine is great for reactive data. htmx helps manage apps with many server calls. You don't necessarily need the full React or Vue package, if your app isn't so complex.
But if it is, I think you'll be glad to have them.
Managing just your application's state, while letting some template logic know where to embed that info into the app, scales far better.
If you measure complexity strictly by the amount of code running, then a React or Vue app will likely be more complex. If you consider just the actual application logic, it's usually far simpler. This is especially true if you utilize components, which lend themselves well to rapid development with fewer side effects.
> We’ve noticed that there’s been some confusion between our company, Codium (now Qodo (formerly Codium)), and another company, Codeium.
https://www.qodo.ai/blog/codiumai-or-codeium-which-are-you-l...
I've never seen anything like that before. It feels like a search+replace operation gone awry.
Mojang made large improvements to the lighting engine in 1.20, bringing it in line with the performance mods Phosphor[1] and Starlight[2]. Despite being deprecated now, they might still offer some useful insight into how to approach such a system in a performant way. You'll need to be mindful of the licenses, but it's likely easier than reverse-engineering Minecraft (even with mappings).
I don't see it listed, but is there support for block breaking/placing yet? Presumably this would require light recalculation and a chunk update on the server.
Finally, do you plan to add advanced features like scoreboard, teams, or command block parsing in general? Mojang has at least open-sourced Brigadier for that.
Cool project. Hope to see it mature to the point of making servers easier to run on low-end hardware.
Moving interactions to JSON in many cases is just a better experience. If you click a Like button on Facebook, which is the better outcome: To see a little animation where the button updates, or for the page to reload with a flash of white, throw away the comment you were part-way through writing, and then scroll you back to the top of the page?
There's a reason XMLHttpRequest took the world by storm. More than that, jQuery is still used on more than 80% of websites due in large part to its legacy of making this process easier and cross-browser.
https://godotengine.org/article/godot-engine-was-awarded-epi...
I find that view to be overly pessimistic, and not reflective of what health care providers actually do. Practitioners of all sorts work hard to cure and prevent diseases every day. Every time a cancerous tumour is removed, it significantly reduces the chances of that person needing follow-up care. Every vaccine that is given reduces future hospital visits. Every piece of good advice to exercise and eat right keeps somebody away from the doctor, rather than turning them into a repeat customer.
Doctors aren't evil. They aren't scheming to lock patients in by offering suboptimal treatments. They provide the best care that they're able, within the limits of the knowledge and resources available to them.
There is a large span of people between gray beard programmer and lay person, and many in that span have some concept of open-source. It's often used synonymously with visible source, free software, or in this case, open weights.
It seems unfortunate - though expected - that over half of the comments in this thread are debating the OSD for the umpeenth time instead of discussing the actual model release or accompanying news posts. Meanwhile communities like /r/LocalLlama are going hog wild with this release and already seeing what it can do.
> any software developer should have a firm grip on the terminology and details for legal reasons
They'd simply need to review the terms of the license to see if it fits their usage. It doesn't really matter if the license satisfies the OSD or not.