kevinob11

Does that mean they will be in cars in ~6 years?

We love PBS kids for my 2,4,6 year olds. I don't feel I've seen any content I'd consider politicized on there.

I really wish Apple would release iMessage for Android. I know they never will, and I know I can just use SMS / MMS / RCS or WhatsApp or Signal or whatever. I'm just really tired of the default app for iOS not being able to interop with Android. Every time someone from my wife's family sends (iMessage) her a video and its low quality on her phone (pixel) and she asks them to email it and they say "What is wrong with your phone" a little piece of me dies inside.

While this would certainly be good information I'm not sure they are the _only valid_ temps to test range at. Surely what would be most reasonable to report would be your day-to-day environment. That being said electric cars do seem to have their range affected by temp a lot more than IC cars, and as someone who lives in the Pacific Northwest I do feel like their ranges should be quoted regionally, though that does seem like a lot of work for something that was pretty easily researchable going in. That all being said, it would have been nice to know that my average in WA would be about 5% below the Southern California average.

Full disclosure - I own a model 3 and love it

+1 for on-prem. I tried gitlab.com first but it was very slow (this was years ago, YMMV) but on-prem has been rock-solid and fast for us hosting ~100 projects. One thing I've been surprised by is how easy updates have been, I don't think we've ever had to even reconfigure anything, including runners. I know it seems like that is how it should work, but I've had a lot of opposite experiences with the open source tier of tools.

@josegonzalez, thanks so much for all of your work on Dokku and for being so responsive in the community for the last couple years. We tried Flynn at one point and had enough issues we moved back to dokku within 2 months and have been happily living on it for years now. You helped me directly with an issue with DB naming at one point, much appreciated!

I love your site, thank you for building it!

This has been my experience, react is now a tool I reach for to build apps that require a very high level interactivity with a non-form based ui. For more standard workflows Django with a bit of vanilla JS has become my go-to tool.

Our team has never felt more productive and the dev learning curve is much less steep. Clients are happier with the results, and the apps feel much more maintainable because there are less pieces to break / update / manage in the production environment.

Just me, spend ~15 minutes sanity checking then just ask them to test again.

I had the same issue once and was convinced that I must have pointed the reviewer account to the wrong server. I spent 2 days debugging before I finally asked the reviewer to check their network connection, I was approved the next day. They did send a nice response admitting the issue was on their end, lesson learned.

When I first saw the dot I was very excited thinking it was exactly this, but it appears it is just an echo with a lower quality speaker and a simple cable (and bluetooth) you can connect to your own speakers. A bit of a bummer synced timers and playing the same music through a couple of Echos in different rooms would have been a better use case for me, but perhaps I'm the weird one.

I really like axios for the api calls, super simple and uses the promises syntax that we use throughout our app.

Fair enough, though I do have some experience with shipping to production.

I do have quite a few other issues with sails and waterline (ORM). Waterline provided lifecycle hooks, but limited their power and had poor documentation on extending them. Same for sails core itself, it had hooks for writing modules and extensions, but no one outside of the core team knew well how to use them. As for migrations I ended up doing all of my own migrations with knex, I'd love to see knex or sequelize be the core of a new ORM, rather than a quickly cobbled together sql module.

Trails has promised something better on a lot of these fronts through modularity, I hope they deliver.

I think it is only part of the core team, frustrated by the lack of progress on sails, so maybe they want some of the same changes you do. Also, while I had my own frustrations with waterline, the auto migrations were meant to speed up development, they were never meant to be used in production and can be turned off with a single line if code.

Thanks, I know alpha release for trails is in the next few days, when do you expect to have a production release? I know trails is supposed to have a pack that allows you to use it with current sails codebases, how well baked do you expect that to be? Will anything in the sails codebase that goes beyond the simple controllers, models, services, config need to be refactored? For example: custom blueprints, sails hooks, code based on model definitions pulled from sails config, etc.

I've been using sails for about 18 months, this has me pretty worried and I've experienced a lot of the issues (bugs, long delays on issues and pull requests) others have described. What other nodejs stacks (hapi + ORM?, kraken + ??, etc) do others use to create server apis without having to write a ton of boilerplate for each route / model?

The banks have taken some losses as well.

https://en.wikipedia.org/wiki/Greek_government-debt_crisis#c...