217 karma · joined October 29, 2018
But there really is no reason to get rid of the unix timestamp as a measure of time and this measure may stay around for a long time. This may mean that people in the future might consider 1970 as year zero where modern civilization began.
What js does is that it allows you to dynamically update the contents of your website like changing an image when you hover over it for example. This is something you can actually do with ALFI by itself without having to depend on a second language like js. I'm glad you asked this question.
The lack of styling I do understand can make it feel as if your site lacks personality when all sites look kinda the same so I see your point here. I might later allow some minor themeing, like say allowing you to select a color scheme, with the understanding that this might be ignored by the user. I will have to think about this more. What you will never get to decide are things lika margins and paddings and things like that.
I don't think you can compare Markdown with ALFI like that exactly. Markdown will generate HTML in the end and it is the resulting HTML that you need to compare with because that is what the browsers understands. Also, Markdown only solves the trivial cases and that is why it can be kept simple and readable but how do you for instance create a three column layout in Markdown with an image in the middle column? I don't know, maybe there are extensions for that these days too.
It would be interesting to have a Markdown to ALFI generator, but I suspect that when you are used to reading ALFI code you might find it to be a bit overkill because even though I am a bit biased of course I do think ALFI is pretty readable.
Also, there is no intentional OOP or funcional aspects, I did not quite understand what you wanted to convey there.
http://www.blunder.se/screenshots/s1.png http://www.blunder.se/screenshots/s2.png http://www.blunder.se/screenshots/s3.png
Replacing HTML/JS/CSS with a language called ALFI. It is stupidly simple in its design but still very powerful. Similarly to HTML you use it to create widgets, place them, and define their behavior. It is humanly readable like HTML but line-based instead of markup-based. Instead of nesting it uses references. This allows it to be streamed.
A big difference is that the language itself doesn't allow styling (like CSS), the downside being you get less flexibility but the upside being it will render correctly on any display with any resolution.
For this I have also written a new type of web browser called NAVI which takes ALFI code and produces (somewhat) beautiful widgets and renders them using OpenGL.
Source for both ALFI and NAVI: https://github.com/jezze/alfi
My own ALFI website: http://www.blunder.se/
You need NAVI to actually browse blunder.se properly. otherwise you will just see ALFI code. Also this is still very early so all features are not done yet.
With that said, his visions are sometimes too unrealistic like his vision of self driving cars. He really underestimates how hard that problem is. Saying he will have a self driving car before this year is over is borderline stupid and that pisses me off.
Instead I thought it would help to make code reviews optional. It is dangerous and I wouldnt recommend it for everyone and it only works if you have a CI pipeline in place of good quality. What you do is that you allow people to push directly to master, then you have your CI system continously testing all the latest commits and only if something breaks will it report it back and then the person who wrote that commit needs to fix it. I have never tried this in a real working environment but I think it would decrease friction a lot and just be slightly worse in quality. Also instead of pushing to master you could have a staging area that automatically pushes to master if it passed the tests. That might even be better actually.