gothy

EdgeDB is looking like a dream db (with batteries included) to me, congrats on the launch!

I wonder if you might wanna join efforts on building your cloud offer with guys at https://neon.tech/ (i'm not affiliated, but I'm waiting for your cloud offering)

Also, this "Platform limits" page doesn't make much sense now https://zeit.co/docs/v2/platform/limits

They were in that space already.

With this new pricing model, it feels like we're getting a generous "free tier" on the platform, but it's implicit.

The "Hobby Plan" section in the ToS sounds like a risky thing to sign up for https://zeit.co/legal/terms#hobby-plan

I'm a solo dev. I won't sign up for the "Pro" plan in the foreseeable future

It's hard for me to decide if it's genius or insane. This "fair use policy" really makes me nervous about the whole thing.

New Surface 3 Laptop combined with WSL2 looks promising.

Also, there're rumors on MBP 16" with a fixed(?) keyboard...

I'm looking at FaunaDb very closely, seems like a nice "all you might ever need", but a bit unfamiliar at first glance.

Hi Dan,

any chances you and your team are working on a GraphQL access layer for the Firestore?

It feels like nested queries(using refs for relations), basic mutations and (especially) graphql subscriptions would be a great match with Firestore and a big improvement in dev experience, imho.

> Well, yeah. If I'd like to hang myself, I'd pick a technology with fewer correctness guarantees. As it turns out, that's not what I want. This is self-evident.

That's exactly what I'm talking about. I'd also like to pick up some "silver bullet", like Elm(if I got you right), for any new project.

Unfortunately, real world is usually a little bit more complicated than "I'm free to pick up any technology that I want. All browsers are the same, their behavior is consistent, mobile web is pure joy and all of our users know their plugins might cause an issue to our app, therefore they're disabling them when they launch our app".

Anybody who does webdev knows that. Different projects, different requirements(sometimes very, very strange), brand new requirements right before the release, deadlines, etc. There're lots of things you have to deal with to end up with a good website\app. Picking a language with nice "correctness guarantees", is not going to help you much.

There were times, long time before 0.19, when there were at least discussions on effect managers, extending the type system, native modules were a nice escape hatch to fix your problem at hand with nasty browser bug or even Elm runtime issue. Those were times when I was so excited to use Elm, did some tiny (sub)projects in it, did a workshop at the office.

Since then, many things have changed to the worse, imho. Some features were removed, not even deprecated. No public discussions, no roadmap, no bugfix releases, no escape hatches for special cases. But who cares what some random guy on the internets thinks :)

Don't get me wrong, I think Elm is a great experiment in the land of static languages, lots of great stuff is getting into mainstream languages(like Elm architecture, error msgs). I still hope we'll see the 1.0 version and things might get better in terms of feature stability, feedback and building things a little bit more complex than counter apps without hitting even more pain points than we have with modern JS\TS.

I was(am? will be again?) a fan of Elm. Constraints can be helpful and even liberating(in some sense). But that's something that should be balanced carefully with other things, like rules\laws that are clear, universal and follow the common sense. Unfortunately, during my Elm journey, I've found that's not the case for Elm.

> Freedom is the rope with which I can hang myself.

If you'd like to, why not? It's up to you. You're not forced to do, though.

On the other side, being a hostage of some secret plans in "people in power" minds, you might be forced to do any kind of staff. New constraints are here and they're enforced on anyone. That's a catch with constraints, you can be OK with existing, but you'll never know what comes tomorrow.

This is a must read book even if you're not building a database :)

> We will be postponing this event until we can deliver a more diverse slate of speakers.

Like until the time only 50% of speakers are homo sapiens?

I've got the very same thoughts.

My 2014 15" MBP is mostly fine, however it needs some cleaning and anti-reflective coating issue has become really annoying lately. 2015 vs 2016 was hard since there's so little feedback from actual users(power\professional ones) and this post is really helpful. I haven't heard anything more annoying(to my ears) than this new keyboard.

Still buying smth 1.5 years old(instead of 2.5 y.o.) not to satisfy your expectations, just to meet your needs(old ones, but with no stain issues)... Is it the world that "pro"+"mobile" Apple users should live from now on? :\

I can. Many friends have left during last year or so. Not sure if this is the only reason, mostly it's just a wish to find a better place to live and raise kids.

Location: Ukraine

Remote: Yes

Willing to relocate: Maybe

Technologies: mostly front-end - JS, SASS, React/redux, Backbone, Node. Interested in Elixir.

Résumé/CV: http://gothy.me

Email: dmitry.utkin@gmail.com

Interested in building web projects from top to bottom, FP, scaling systems.

Location: Ukraine

Remote: Yes

Willing to relocate: Maybe

Technologies: mostly front-end - JS/Coffee, SASS, React/Flux, Backbone, Node. Also played with Go, Elixir.

Résumé/CV: http://gothy.me

Email: dmitry.utkin@gmail.com

Interested in building web projects from top to bottom, FP, scaling problems.

Hehe, I've done that when I was younger :)

I understand you very well. My todo list called 'stuff to check out' grows so fast that sometimes I'm thinking about clearing it out and just start another one.

Location: Ukraine

Remote: Yes

Willing to relocate: Maybe (in 6-12 months)

Technologies: mostly front-end - JS/Coffee, SASS, React/Flux, Backbone, Node. (Past: Python/Django, Android. Also played with Go, Elixir)

Résumé/CV: http://gothy.me

Email: dmitry.utkin@gmail.com

Interested in building web projects from top to bottom, UI\UX, solving scaling problems.

Location: Ukraine

Remote: Yes

Willing to relocate: Not at the moment.

Technologies: mostly front-end stuff currently - JS/Coffee, SASS, Backbone, Node, React. Past: python, java, android/j2me. Played with Go, Elixir.

Résumé/CV: http://gothy.me

Email: dmitry.utkin@gmail.com

Interested in building web projects from top to bottom, UI\UX, solving highload problems.

> Your time would have been better wasted on building a framework for an already established language

Don't we already have more than enough frameworks for established languages? :\

Node processes do not share resources. Exception is some shared libraries that they might use like any other process on the system.

Yes, modules are loaded and used independently in V8. Node just wraps it around and adds some additional features.

Location: Ukraine

Remote: Yes

Willing to relocate: Not at the moment.

Technologies: mostly front-end stuff currently - JS/Coffee, sass, backbone, node, react. Past: python, java, android/j2me. Played with Go, Elixir.

Résumé/CV: http://gothy.me

Email: dmitry.utkin@gmail.com

Interested in building web projects from top to bottom, user experience, solving highload problems.

I guess it's about marketing Hive to people. If you bring them 100 customers, and 5% of them will pay full price for Premium. Why shouldn't they give you smth in return?

So hitting Ukrainian planes is OK? There wasn't any kind of terrorists that I'm aware of who got access to such a sophisticated weapons. And no one of those 'monkeys' could even handle with that 'BUK'. It's obvious that only trained army team could make this launch and it's obvious for us(Ukrainians here) that after brutal annexation of Crimea , this sick freak wont stop until he gets punched in the face. He doesn't understand any other language other that rude force. Ukraine is weak, much weaker that Russia now. Mostly because the very same Russia-oriented mafia clans. Former government of Ukraine is now hiding in Russia and they wont be judged there. Russia's mission number one was to prove that Ukraine is a failed-state. This is the main reason why all this happening. Max explains the rest in his post.

Best decision ever.

Using CS for about 1.5 years now. Yes, there're ways to hurt yourself with bad CS code. This is also true for Python.

When developer writes some fancy one-liner in CS or Python and I'm reviewing his commit, I just ask him to come over and explain what this thing is doing. Sometimes it takes more than 20 second to read and explain even by author. Then I say: "You wrote this line an hour ago and it's already hard for you to understand what it does. Imagine you'll need to change it in a month. You'll hate yourself. Go and rewrite this code explicitly to help yourself in the future."

If you force yourself and teammates to write explicit code, you get all the pluses of CoffeeScript avoiding bad readability.

Node is not for everybody. Node is not for everything.

2 hasenj: try using coffeescript to get expressiveness if you're coming from Python(like I do). You'll be much more comfortable with it. Especially when you're using it for both frontend and backend.

Node was a "why not?" choice for my last small inhouse realtime analytics. I could write it in python, but I've been writing LOTS of CoffeeScript recently so I've tried to go with node and redis. And it was a perfect fit for this task.

I'm pretty sure I wont use it for some complex business logic or number crunching. But that's not because I'm afraid to loose maintainability or peace of mind. It's because that would be just stupid, there is a lot of better tools for this. You should keep in mind whats your platform nature, whats it good for.

Every contending platform or language has it tradeoffs. I like ErlangVM features and philosophy, but I can't pass over the language weirdness. And VM speed sucks. And the community is much smaller. Nodejs is booming, you should agree on that.

Go is great, I'm planning to use it for my next "why not?" project. But it takes a lot of things you love in dynamic languages away. You choose between "program performance vs programmer performance". And again, the community and adoption is taking its first babysteps.

I guess it is. Not for everybody though.

I've played a bit with the initial Fire tablet and I was really surprised with overall UX. Some Chinese "noname" tablets felt like a better option than "this".

Apple has really high standards in producing their products and user experience from store to watching a movie on iPad. Amazon is good at providing services, but they fail at the overall UX. Maybe that's going to change, maybe HD 8.9 is a huge step forward(i just don't know yet). But for me, the overall experience really matter much more than a price badge on a box. IMHO.

Finally!