HN user

CircleJerk

13 karma
Posts2
Comments9
View on HN

I liked React ideas it's just that it feels incomplete not to use the entire stack you mentioned. And it's too much for my taste. I'm sure webpack works fine for most people it's just that the possible edge cases with the black box that is the compiled modules files and lack of good documentation makes me lose my sleep. Combined with the alpha state of the rest of the ecosystem is not really an easy choice for a paranoid developer like me. I also faced a lot of small inconveniences because I'm using Vagrant. IIRC there were options like watch-polling that was available as a cli arg but not on the config file. And the usual CORS problems that I had to solve.

My english is awful, I was trying to say it's not really a SPA that I'm making. I want to keep the routing mainly on my back-end and only do ajax calls to my API where needed. But if it's not another alpha-state component I would love to have the added possibility of using one or two extra routes on the JS side. It's just that checking the most popular repos and reading things like these is awful: "We are currently working hard on some major API changes for version 1.0."

Is like "mini-SPA's" on a few places that deal with too many data sources and would be a pain to make my users change screens.

I really enjoyed doing "one way binding" and some ideas around React though.

Bootstrap 4 alpha 11 years ago

I'm launching a not-so-critical thing in 2 or 3 months, currently using Bootstrap 3.

Is it safe to adopt 4 right now, to be more future-proof? I don't mind bugs that eventually will be fixed but is the API stable enough?

GlassWire, EMET and AppLocker are new to me but they sound promissing!

Why do you prefer Avira? I find hard to compare since the reviews are usually personal experiences without any real data, and since they are usually closed source it's even harder.