Frontmacs
github.com
Frontmacs
1–10 of 100 posts
Re: Frontmacs
#2Some screenshots could be nice, probably most people are not tend to try it out until they see a screenshot.
Anyway, I am a simple man. I see people using Emacs and I become happy.
Re: Frontmacs
#3Slightly off-topic, but:
> Most of the planet doesn't treat editor configuration as software. We do.
This is so true! And it applies to many, many other types of configuration as well.
Re: Frontmacs
#4It claims to be "Awesome by default", but does not tell much about what that actually means.
Re: Frontmacs
#5Some screenshots could be nice, probably most people are not tend to try it out until they see a screenshot. Anyway, I am a simple man. I see people using Emacs and I become happy.
Agree! I am not a developer or an overly technical person and I recently started using Emacs because of an article here (using ido and org mode). I like it but I'm not fluent enough, or know enough of what it does to switch to it for everyday tasks - but there's a beauty in navigating file systems, creating files, switching windows all with your keyboard.
Does anyone know if you can actually write code on Emacs, like HTML/CSS/Javascript?
Re: Frontmacs
#6Slightly off-topic, but: > Most of the planet doesn't treat editor configuration as software. We do. This is so true! And it applies to many, many other types of configuration as well.
Reminds me of the evolution of Lua https://www.lua.org/history.html from a configuration language to a full blown programming language.
Awhile ago, we've used this code as data approach in a game development studio for everything. For example, maps/levels were stored as a Lua scripts that get executed on load and contain a sequence of PlaceObject, SetProperty, etc invocations.
It doesn't come without drawbacks, though. For example, Autodesk Maya stores scenes as Mel code (as a bunch of createNode, connectAttribute, setAttribute commands). This script gets executed on load in a single thread (utilizing a single from your N cores) and scene loading can take ~30 min on large scenes. Security is also an issue but it's fixable with proper environment sanitation and sandboxing.
Re: Frontmacs
#7Great approach. Now what does it do? (Or rather, what can I do with it specifically compared to other distros, and how?)
Re: Frontmacs
#8So many buzzwords and startup like speak but no "made with love"?
Re: Frontmacs
#9Some screenshots could be nice, probably most people are not tend to try it out until they see a screenshot. Anyway, I am a simple man. I see people using Emacs and I become happy.
Agree! I am not a developer or an overly technical person and I recently started using Emacs because of an article here (using ido and org mode). I like it but I'm not fluent enough, or know enough of what it does to switch to it for everyday tasks - but there's a beauty in navigating file systems, creating files, switching windows all with your keyboard. Does anyone know if you can actually write code on Emacs, like…
If you mean using emacs as your code editor then yes, that's the main purpose of emacs for most users. However there's other hidden eastereggs such as M-x pong, M-x tetris or why not try M-x doctor if you're feeling a bit down.
Re: Frontmacs
#10Slightly off-topic, but: > Most of the planet doesn't treat editor configuration as software. We do. This is so true! And it applies to many, many other types of configuration as well.
Reminds me of the evolution of Lua https://www.lua.org/history.html from a configuration language to a full blown programming language. Awhile ago, we've used this code as data approach in a game development studio for everything. For example, maps/levels were stored as a Lua scripts that get executed on load and contain a sequence of PlaceObject, SetProperty, etc invocations. It doesn't come without drawbacks, thoug…
This is an interesting aspect, but slightly different from what I had in mind.
Just because you treat data as code doesn't mean you have to force it into a Turing-complete language. It just means that you should document it, format it properly, put it into version control and deliver it for deployment.
Moreover, Turing-complete languages are more of an anti-pattern here. The proper design pattern here is the Rule of Least Power:
https://en.wikipedia.org/wiki/Rule_of_least_power
It means you should choose the least powerful language suitable for a given purpose.
And this is where DSLs or "data as code" can play its advantages: Not just makes it things shorter and simpler, but you can also force it into a less powerful language, which allows you to eradicate certain types of bugs and security issues by not making them even expressible anymore. Moreover, you can run your data structure through different "interpreters" doing different things with it, which is completely inpractical of your data structure describes a too powerful language.