719 karma · joined March 23, 2018
https://brandonowens.me/
let email_address = [{ 'brandon', '@', 'elegantframework.com' }];
Ironically, the guy who created the IBEW, Henry Miller, was himself killed on the job after making contact with a live wire and falling off the pole and hitting his head.
In the early days of electricity, the workers had no understanding of the thing they were working with, and they certainly weren’t given proper tools.
The voltage tester of the day was licking the wire to see if it was live. A method thought to save people after electrocution back then was to stick your fingers in their rear to give them a sudden jolt lol.
I’m working on a fun side project now that was inspired after emailing him.
When YC asks me to come out for a demo, I’d be most excited to finally meet him in person lol
What's the best way to contact you?
Is the pricing for the hosted version?
Interesting to note the mention of servers!
I actually forsee a wave of JavaScript innovation within the concept of a traditional backend server coming soon, and it's interesting to see them mention a server here.
I've forever been from the school of "Rule number 404: thou shall never use JavaScript on the server side.".
But with React 18 and the serverless wave, I can totally see myself writing backend controller code in TypeScript that gets deployed by Vercel in the near future.
Also, Amazon doesn’t “clear” out their warehouses. They charge sellers to story inventory in their warehouses. The longer items sit unsold, the more amazon makes off of the seller in FBA fees.
It feels like the community wants it, but Tumblr themselves don’t understand what people actually want.
I’ve been working on a side project in my off time, and my wife tells me that what I’ve built is like a “Tumblr” lol.
What do you think? Is this something worth pursuing?
Things were “mehhh” for developer interest for the first month or so, as a I was working off of an internal todo list. I didn’t think anyone cared about my 300 line long todo.txt file, but then I started to wonder if I should find a way to put that doc out in the open for developers to follow, and possibly jump in and contribute.
I had a hinkling that I could use GitHub issues to help with this, but I believed the title “issues” would hurt my project. I was under the impression that a new open source project with a single contributor, and a ton of open “issues” would look bad to developers.
I started to inquire with devs on IH and hear about using issues for feature tracking. Much to my surprise, I got an overwhelming “yes, you need to use issues”. I was also told not to worry about the misleading “issues” title, and that enough developers were knowledgeable enough to know they weren’t just bug reports.
As I started to open issues, and ask for help; surprisingly I started getting traffic and interest. The more issues I opened, and the more open I was online about my code and plans for it; the more followers and contributors I’ve gotten.
My plan at this point is to just follow Gitlabs model, and go full open transparency with everything.
My side project mentioned above can be downloaded here: https://github.com/elegantframework/elegant-cli
Please explain why they needed to create their own style?
Just a plain old dumb JavaScript file, but just written in the Typescript superset.
I’d like to hear more of your thoughts on this.
I look at each of the 3 big reactive frameworks as different types of screwdrivers in my tool belt; each with their own pros/cons, and purposes.
As commenter above said, I’ve seen a mess of all 3 frameworks; and I’ve also seen some beautiful works of art, with even Angular too lol.
Next/Nuxt really take Vue and React to a whole new level when building a wet application.
I’m very well versed in all 3 of big reactive JavaScript frameworks, and React is my go to for now.
I switched from Vue to React as my default after struggling with complex data tables in Vue; when React had a bunch of libraries on GitHub that would work for my project at the time.
The final nail in the coffin was a contract requirement for .Net core framework, and it came bundled with React in it already. From there, I found Next, Typescript, and Tailwind, and haven’t looked back :)
I gave Astro a look over and promised myself to be open minded; but I wasn’t really digging how opinionated their code was to themselves. Thousands and thousands of devs built on top of each others JavaScript improvements for years, and then Astro comes along and decides that us developers need to learn a new “.astro” syntax as well.
Imagine if Tailwind or Laravel forced you into funky .tailwind/.laravel named files because they felt a certain way about their name.
I took this as a sign that Astro might become a very money hunger shark at the first drop of blood like other popular CMS providers have done in recent memory.
I’m working on a free open source side project now for fun with the goal of helping more people create and own their own content online, without paying an arm and a leg for it.
I’d love more support and feedback if anyone has any to give :)
If you feel that developers need an open and extensible product for creating content, please give me a star, and open some PR’s and issues.
It’s just plain old dumb boring static text that is being moved around the web.
The internet was essentially created so that CERN could share plain old text documents with others remotely.
Why do I need a big bloated overly complicated PHP webserver that talks to an overly complicated database, when it’s just plain old static text after all?
Docusaurus is an amazing tool for startups, but it started to show its weaknesses as we tried to scale it.
Our project requirements needed something more, so I ended up forking Docusaurus and started working on my own free open-source solution.
Check it out, I’d love to hear what everyone thinks! :)