@blakeyrat said in Boomla:
@homoBalkanus
learn problems of a concurrent environment - whatever it is,
"I don't know what problems these are, but trust me: Boomla solves them!"
Boomla is a simple platform for websites.
In Boomla, everything is a file, there is no database.
Ok... so it either has no dynamic content at all, or it performs like shit. (Or, possibly, it has insane race conditions that corrupt data! That'd be fun.)
Is a car fast? Is a filesystem fast? I wrote a filesystem that is faster than those you have experience with.
There are no processes, just files.
Uh. Huh.
Functional systems have no processes. Process is hidden state.
Forget Apache, there is a built in webserver that just works.
But it's not a process! Some...how!
Well, it's not a process within Boomla. It's one outside of its world. From within, you see no other processes, there is just you, a frozen world and you are doing your life synchronously.
Problems with Linux
The Linux filesystem is slow, not concurrency safe, not transactional, doesn’t support storing and searching structured data. Databases are used instead.
But, you're not using a database. You're using the filesystem. So...
As said, a new kind of FS.
Linux manages processes, provides isolated execution environments. The solution is really slow and processes are hard anyway. Websites require a fast, request-response like solution. Currently, website level apps are plain function calls. Isolation was traded for speed.
I guess it's time to switch to Windows/IIS, which offers both.
Interesting.
Linux provides a graphical user interface yet websites run in the browser.
The browser not being a graphical user interface. I... guess?
I wouldn't trust the clown who wrote this to put air in my tires, much less host my websites.
The browser is a GUI, but the GUI visitors see is coded by site developers and not provided by Linux.
As for clown, I do like juggling and stuff.