As of 2025 it's still very much the same.
HN user
whatthemick
http://mhansen.io
Sequelize maintainer, Javascript developer, wantrepeneur
Isn't the AOT story for F# pretty meh? AOT + System.Text.Json requires source generation as best I can tell, which F# doesn't support yet (to my knowledge).
Headers and URI are encrypyed aswell, in a HTTPS request. Only the domain is exposed (when SNI is supported)
https://modeanalytics.com could work for you
For anything that critically needs an audit log it's a pretty obvious choice (atleast compared to when people try to implement audit logs in a RDBMS).
I think it might also have a great deal of merit in prototyping applications quickly - Having the option to do just-in-time/memory projections while later switching to "real" storage seems really ideal to me if i'm just building something to validate it would like to defer those type of tech decisions.
Everything obviously has trade offs, no choice is perfect in everyway.
For me the pros of having data as an immutable stream of events (eventsourcing) is that you get migrations and data modeling for free - You don't have to deal with having to design the "perfect" data model in advance (or worry about schema/data migrations later on) and you can get caching as first level data rather as derived from another store.
Have you tried JSONB and can you expand on how it does not give you speed and flexibility?
I would expect those events to be triggered by action though, then it wouldn't be persistence ignorance.
Neither Sequelize nor Bookshelf has persistence ignorance as far as i know.
Likely also better performance with just using Knex. Any ORM likely adds overhead, Sequelize definitely does, although we keep working on reducing that overhead - But inevitably features === overhead.
It's sort of his style.
"with tools like browserify i have to look at the folder structure"
I don't think Browserify cares about your directory structure as long as it can find the entry file it will figure out the rest based on your require calls (and also make sure they are in the right order dependency wise)
Or Denmark
SEEKING WORK - Remote - Copenhagen, Denmark
Full-stack developer with focus on single page apps and node.js
Experience with building startup products and implementing tracking.
Love building "elegant", maintainable, robust and well-tested applications.
Postgres/MySQL rather than NoSQL (i'm also a Sequelize maintainer)
Email: maker@mhansen.io
GitHub: github.com/mickhansen
You need to consider how much of your app needs to be realtime.
Do likes, comments, whatever absolutely need to be updated in realtime? If they do, you should consider going with a full realtime service. If not, i would go with a backend that you feel comfortable with and build realtime where you need it.
I'm building a Ionic (AngularJS) based mobile-app aswell and went with Firebase for full realtime, but in hindsight i would probably have had a better go with using a RDBMS on the backend (which i'm way more comfortable with) and used Socket.io or similar for the parts that really needed realtime.
Kinda screws over the scandinavians, and a lot of other people i'd suspect.
I'm personally not a huge fan of the eventemitter for cases where an event is only ever emitted once (an sql query is done or similar).
For 2.0 of Sequelize we've moved almost the entire codebase to promises and will encourage users to interact with Sequelize with promises.
I've been thinking about something similar, an autoscaling job queue that could run off your own servers (via API) so you could decide the pricing/power you want.
Perhaps they named it for Annyong but changed it for the easier search results?
"Next, there's a short Skype/mobile call that basically makes sure you can communicate in both Polish and English"
You hire people remotely, but they have to speak polish?
Name and logo immediately made me think of Freshbooks.
There's also Sequelize (http://sequelizejs.com/) which is increasing its focus on Postgres specific features.
Same, but it's been a year so far since the initial request opened so...
I'm interested in this aswell. I assumed "Show HN" was the appropriate thing since you clearly state it's a type of self-promotion.
I personally appreciate people being upfront about it being promotional, StrongLoops latest "tutorials" have been a bit of a sinner in this regard. They usually provide great content but always mention their own services (which is fine in my opinion but it should be obvious from the get-go).
Edit: Perhaps the prefix is removed to remove any bias, perhaps people are inclined to be more positive towards user contributions - Perhaps by removing Show HN you let the product live on its own merit, rather than any type of emotional bias.
Without equity? Not a single day.
Interesting, that does provide a highly consistent base as you say. I might just have to try out Closure with Om/React for my next project.
Yeah i'm struggling with this aswell - I basically dropped out of the danish HS-equivelant.
I think i'm a pretty decent coder, but i have next to none experience with algorithms - Usually i'm pretty good at learning new things just by trying out and reading up on them (server management, new languages etc).
Algorithms is the one that really seems to require an education, i'm having a hard time learning that stuff on my own - But i'm giving it a go by working my way up to linear algebra on Khan Academy and reading examples on Naive Bayes etc.
I like the idea of React.js and immutable data. But i'm not a fan of the lisp syntax, am i missing something?
How do you figure?
That seems like a discouraging chicken-and-egg problem for unconnected startup founders.