The remote can be a shared directory that multiple users have access to, and the working directory is private where each user only has private read + write access.
I live in the pacific NW and feel that we do largely have those but people don't know about them or don't want to use them. For example, the easiest way for me to get to Portland/Seattle/Vancouver is by far the train. In none of those cities would I recommend driving as public transit is better in almost all cases. I live in a medium sized city and even here we only drive about once a week. So it is totally possible but it takes some additional planning and tradeoffs that many people don't want to do.
Most cities have alternatives to driving simply because they geometrically have to. When I say there should be viable alternatives to driving everywhere, I mean small, rural towns as well.
I live in a well-connected, medium sized city in the North East, without a car. My parents live in a very rural town about 300 miles away. I can walk from my apartment to a local train, and then from there get to an Amtrak that will take me to 30 miles from my parents house. While I could technically bike that, that is quite the hike to make after 300 Amtrak miles. Especially fearing for my life sharing the road with distracted drivers.
There is no reason for there to not be regular bus service from the city that I get off Amtrak in to the larger town between my parents and the station, and between my parents smaller town and the larger one. In a modern, developed nation I would be able to make that trip entirely by transit and walking.
And by "modern" I mean as of the 1860s, because back then it was connected by train!
As you mentioned, electric bicycles flatten terrains (so do wide gear ranges), and jackets neutralize climate. There seriously isn't anywhere that is inappropriate to cycle. The only major limiting factor for people feeling comfortable biking everywhere is the threat of violence due to people driving cars.
Lightening is another limit. I'm going to drive to work today because there is a 20% chance of thunderstorm when I'm planning to going home, and that is too much risk.
Actually no I can’t recall the last time I tried to ride a bike in the snow. But I know inherently that snow itself would be alright, but snow is almost always accompanied by a layer of ice below, which simply can’t be fine. This is the case in Canada at least.
Google could loose 70k active users and it wouldn’t even register as a blip. They have like 50,000-60,000 TIMES as many active users.
I’m one of those 70k people and support Kagi, and I also strongly believe in companies succeeding and sustaining themselves on a small scale like this. I think our economy would be healthier if it was made of many, many small companies, not a few massive ones.
But we can’t argue Kagi is anything more than a super niche product, for now. :(
Did you mean to reply to someone else? You can set the date manually on the Daylight and even if you have trouble, you can just use a different app. It's just Android.
There are companies that will make deals with tens of thousands of book publishers and provide storage and access for millions of books, magazines and comics? I suppose they will do it for free?
For (others) reference the oldest bits of code in our software are from the mid-late 90’s and the oldest systems still paying for support rely on parts to build that is not available at any price, its all just made of unobtainium, whereas I can sell them a brand news that does everything they have today and more.
Ooo this is nice. I may have to try to get this working with my personal setup using Emacs and Sway.
My long term vision is to make an Emacs implementation that is compatible only in philosophy. It would use Guile instead of Elisp, default to bindings that are more familiar to people coming from more modern systems, and would be built from the beginning with concurrency and graphics in mind. For now it remains a dream though.
Nope! I should have elaborated, but by "graphics in mind" I meant full support for graphical applications. I want it to be a Wayland compositor. It would either be used as a top level compositor like EXWM, or as a nested compositor, like how gamescope is used.
I want it to be as easy to make scripts to automate graphical applications as it is to automate textual ones in Emacs or shell scripts.
As I said in my other comment in this topic I actually would love to see an arch where the UI portions are split up with a background daemon holding buffers, lisp execution etc and then IPC to frontend pieces for window management and buffer editing.
So window management can be done by ... a window manager, but with intelligent interaction to the editor pieces so you don't lose all the awesome emacs stuff.
EDIT: I would say however that something like lem is probably more amenable to that refactoring/restructuring than GNU emacs, which is a single-threaded monolith.
I'm familiar. The difference is that this is targeting source compatibility with existing Elisp. I don't feel like that is worth it for most people who would be interested in what I want to build.
Pfff... it's like my teenage daughter who's never driven a car brags to her friends how Mazda is better than Toyota, because "she switched".
"Using Emacs" means actively reading, writing, evaluating Lisp code. How many packages have you written? If not too many, I'm afraid, you're only "riding it", not "using" it, just like my daughter has been riding in one car and now in a different one.
There's a huge fundamental gap between Emacs and VSCode. In Emacs, the editor is the Lisp runtime. Every piece of the editor is a live Lisp object you can inspect, redefine, and compose at runtime. There's no boundary between "editor" and "extension" - they're all just functions and variables in the same image. VSCode doesn't offer anything remotely close to that.
Without understanding that gap, there's no understanding of what Emacs actually is. There's no "switching" between Emacs and an editor/IDE. "IDE" is a much smaller category than what Emacs actually is. You switched editors while not realizing you gave up something that isn't an editor.
A bit harsh, but 100% on point. THIS is why emacs is fundamentally different to the core of what emacs is vs all other editors - you’re driving a Mazda, but you’re your own mechanics with that Toyota
reply