51–60 of 127 posts
Earlier quoted context omitted.
What do you mean by headless UI components?
Basically the ui layer and the backend layer which and the operational layer need to be combined into one seamless tool. Right now you have the write a "frontend" and a "db connection + backend logic layer". And by headless I mean something which builds on what the web provides like buttons but adds a whole lot more of components which are used but are unstyled.
Are you really 15yrs old? is the biggest question here..
Have noticed that teens tend to indeed say they're x old on stuff they're doing.
I know I don't mention my age because I want people to judge my work objectively. (not to imply that I'm a teenager...)
To what does it owe its lightning fast-ness, and how does it compare against other frameworks? Edit: It looks like some of the hot-paths are implemented in C. Interesting! (I would recommend pointing this out in the readme)
this exactly. stop handwaving vague marketing terms, and spell out the technical reasons. this isn't good enough for a show HN imo
edit: just read that OP is 15 yo. ok, i get it. well, treat this is advice to improve your technical documentation, it'll do wonders for your career :)
I am waiting for someone to finally give me just a wysiwyg tool to make web pages and apps so I don't need to program anymore. I just want to make content, not make a machine to then make my content with. It's like building a wood cutting machine when I just want to be warm in the winter.
Aside my web involvement I did a lot of print design as well. For print wysiwyg is perfectly fine.
But how would you wysiwyg for a medium that is inherently multifaced? I mean your window could be small, or huge, portrait or landscape, it could have colors or not, heck it could even be print.
So you won't get what you see unless you replicate the exact conditions under which it was seen when tou made it. Do you want that thing that you scale to stay at fixed size, should it stay at fixed distances to the viewport borders? If yes which ones? What happens if users set their font sizes differently and your perfectly scaled text box overflows? Either that wysiwyg editor has very opinionated choices that won't work for half of the people, or it will have auch a complexity in its options you will be better off with learning css in the first place.
Web is not print, nobody will get what you see.
That being said, if you are really just about content, I would just use the most basic default browser css (so basically none) and html and call it a day. That won't look shiny, but if people want shiny they can do their own styling. Some of my favourite blogs do this.
Other than that I wouldn't discount the fact that a backend can be a crucial part of the content as well as it allows you to do valuable things that are geared towards the consumption of said content, e.g. taxonomy (tags, categories, authors, consistent dates), but also more specialized things like linking between relevant topics, etc.
Of course you could also do that by hand, but then you wouldn't be focusing on the content, wouldn't you?
In the end it is your content and you want to present it in a certain way. If you want precise control over the how, you have to deal with these things — if it ia just about the content, use whatever CMS you like and never look back.
Earlier quoted context omitted.
Basically the ui layer and the backend layer which and the operational layer need to be combined into one seamless tool. Right now you have the write a "frontend" and a "db connection + backend logic layer". And by headless I mean something which builds on what the web provides like buttons but adds a whole lot more of components which are used but are unstyled.
Sounds like a DSL to facilitate building CRUD. I wrote one in PHP and 3 devs were able to build and maintain a 800 page CRUD system with it (still going strong, makes a ton of money). It has complex business logic, is fully unit testable and allows for escape hatches when needed. I'm in the process of rebuilding the DSL in C# with the lessons learned (because Entity Framework is awesome). And might open source.
Flask is decent. Can’t we use that?
Earlier quoted context omitted.
In what world is this an appropriate comment?
I really wonder what that dude was doing when he was 15 years old, should have been a difficult childhood...
Flask is decent. Can’t we use that?
Whatever happened to web2py? I remember that being brought up a lot in these discussions…
Earlier quoted context omitted.
I really wonder what that dude was doing when he was 15 years old, should have been a difficult childhood...
I get what he’s going for I guess but “this isn’t much of an achievement” is sociopathic
I am waiting for someone to finally give me just a wysiwyg tool to make web pages and apps so I don't need to program anymore. I just want to make content, not make a machine to then make my content with. It's like building a wood cutting machine when I just want to be warm in the winter.