It’s not like I’m not using Cursor at all, it just became the 10-20% of my workflow compared to almost 100% before.
8,476 karma · joined September 7, 2018
It’s not like I’m not using Cursor at all, it just became the 10-20% of my workflow compared to almost 100% before.
Growth has its own problems of course (I don't want to estimate the health impact of Coca Cola), but it's a prerequisite of a country not falling behind others.
JSON solved this mostly by standardizing what most implementations were already doing, so that would be a great thing to do.
If git diff isn't documented, the solution is not to create a new format, but to go through the source code and document it.
Edit: LLM to LLVM
I have a male friend under 170cm like that and a woman friend who uses Badoo just because it has a minimum height filter that she sets to 190cm.
My girlfriend also has minimum height that she selected for.
It's just a nature of life.
I just think people have the same right to not work their ass off if they don't see the ROI just like other people have the right to set the minimum height.
If the big US banks are successful, they can have their own one huge fractional reserve that can be used by people around the world.
Now with webui what's important is to constantly add tests around the code base, also if it gets stuck, go through the logs and understand why.
It's more of a management role of ,,unblocking'' the LLM if it gets stuck and working with it than fitting it to my previous workflow.
To tell you the truth it slowed down yesterday as most of the features were done and I had to fix memory/signal/callback leaks, but even that was done much faster than if I did it by hand.
I had done coding on my phone while buying flowers in a gardening store, in my bed waking up without getting out my laptop etc... so yeah, it's not for those people who take the 8 hour work day strictly.
Most of my LLMs made lots of mistakes, but Codex with $200 subscription changed my workflow totally, and now I'm having 40 pull requests/day merged.
Treat LLMs as interns, increase your test coverage with them to the point that they can't ruin your codebase and get really good at reviewing code and splitting tasks up to smaller digestible ones, and promote yourself as team leader.
Cursor just deleted my unit tests too many times in agent mode.
Codex 5x-ed my output, though the code is worse than I would write it, at this point the productivity improvement with passing tests, not deleting tests is just too good to be ignored anymore.
Welcome to 1995.
Also, 70+ year old people who have the hardest time using a mobile phone even if they need to, like my mom are just not even included in the test. She just can't find buttons done with material design.
For a company that was talking about inclusivity for 10+ years, setting 64 the highest age for UX testing is unacceptable.
There are known DNA changes that would probably help all people with chronic diseases, but it's ethically more accepted to go for the more fatal diseases and cleaner cases first, like a rare mutation with a high fix rate.
Ownership is easy, borrowing is easy, what makes the language super hard to learn is that functions must have signatures and uses that together prove that references don't outlive the object.
Also: it's better not store referenced object in a type unless it's really really needed as it makes the proof much much more complex.
In that case it would be true, but it would be hard for me to think that nobody told the leader of Boeing (who should have known it himself as the leader of the biggest airplane company) that putting an engine over the wing is both stupid and dangerous and unstable.
Somehow other models don't work as well with it. ,,auto'' is the worst.
Still, I hate it when it deletes all my unit tests to ,,make them pass''
At the same time for me, while it's super nice, in my opinion it just doesn't differentiate enough from other signals based frameworks to get mass adopted / make CRUD apps that much easier to make.
The problem with remote server/database is ,,what data to sync and when'' by the way, it's very different problem from what your framework is solving.
I loved Svelte until I started using SvelteKit and realized how hard the data synchronization part is.
From the replies I think it mainly went out of favour because of lack of reactivity. I could port PageQL to C/Postgresl/Mysql, but I don't think it would be sufficient for a modern application, as reactivity is expected nowdays. Still, I keep it in mind to leave this kind of development as an option in the future.
Regarding temporary resultsets I'm thinking of adding a #view command instead that creates an SQL view that is shared between invocations and doesn't accept parameter bindings.
The main reason why I want my own full SQL query parsing is because of the reactive views: I want to be able to show 1000 long tables and when a change to a row is made from outside, be able to react to the change without reading the whole 1000 long table again, just push that 1 line change with the websocket. This can be useful for chatbots/chats/live infinite scrolling where the content changes / new content comes in.
Still, it just constructs new SQL queries that are easy to optimize, like SELECT * from (SELECT * FROM T) where id=1 (SQLites optimizer is rewriting these queries quite fast, so I don't want to write my own optimizer, just query builder for reactive SQL).
What's really exciting is that it gives reactivity, reloading, declarative state and a lot of optimizations almost for free, but as I haven't implemented them in PageQL yet, the advantages are less clear.