danman114 · HackerTrans

9 tháng trướcdiscuss

Actually, I don't mind it - I like it - I feel like Mac OS - and especially iOS - got _very_ boring and felt really "conservative" / stocky to me. Everything the same as it always was...

So I am happy for a fresh breeze. I don't mind it. I actually enjoy having some movement in my computers' appeareance, and I feel it's really cool and tastefully done... for my use. Just to mix it up a bit. I'm happy about it. Be a bit whimsical from time to time. Is gudd!

danman114

9 tháng trướcdiscuss

Seconded @the original commenter.

To the posters who say: Ah why should anyone care that you don't care... and actually going to call the post "narcissist"... what the heck, aren't you pointing the gun in the wrong direction? :P

I agree with the sentiment that this is sad. I was very excited for space, space space! And new cool technology and the options it'll bring. It's like we could follow the Apollo project again, but for a new generation, after decades of not-a-lot happening.

So I am sure there are hundreds of millions which are now caught between starry-eyed fascination with the technology and the progress of technology and extending humanity's reach with these biggest and most powerful, while also incredible sensitive and complex machines ever built...

But seeing the main guy unravel into a spit sputtering raving lunatic on social media, going deep into the nastiest rabbit holes available, and showing no concern for the wellbeing and welfare of those requiring protection...

Turns the whole endeavour on its head. Now it looks like the selfish race to capture space for the 1%, to monopolize access and use it as a political tool to further only the very selfish agenda of some detached madmen who don't care about the political "temperature" on earth and the damage they are doing.

So, millions of people turn their heads in sadness, and I completely understand and share that sentiment. It's a shame. It's breaking hearts.

@Elon open your eyes! Enough is enough! :)

Empathy is not weakness.

We'll have you back on the woke team the moment you're ready! :)

danman114

12 tháng trướcdiscuss

Hi! I recently tried to get into Elixir as an antidote to an acute javascript-fatigue...

To my surprise this there isn't really a good mobile story to build mobile apps for both Android and iOS with it, although it looks like it could be a great option for quick turnaround mobile apps with a web- or native frontend...

I know that there is something being worked on, eg. LiveView native: https://native.live/ , but that seems to target two entirely different frontend frameworks, one for each platform...

I started using capacitor as a wrapper for a HTML frontend, but I think I might potentially run into trouble when I'd try to move into production builds...

I think there's some space for research and maybe some nice starter packs / tutorials there... Because I think it is a big and pretty relevant market for browser-based apps, which Elixir seems to be very well suited to!

I'm grateful for any additional pointers, peace out! :)

danman114

năm ngoáidiscuss

Beautifully put.

danman114

2 năm trướcdiscuss

That's really interesting & cool - I'm gonna look into this for sure!

I'd like to mention the Meteor.js framework (https://www.meteor.com/) too, which is in a bit of a transitioning phase right now to Meteor version 3, but is a really amazing full-stack app building solution I and many others have been working with for ~10 years.

It has a lot of batteries included, build system, pluggable frontend frameworks, lots of libraries, based on node.js, meaning it's pretty much compatible with the Node.js environment.

It's based on a really pretty simple syncing strategy for years:

It's original client side data provisioning layer is based on having

a) MongoDB on the Server and b) a javascript-native implementation of a subset of MongoDB in the Client.

Using a publish / subscribe mechanism the client can subscribe to the subset of data relevant to his current view, eg. dependent on the current user & view.

Updating is theoretically possible by using a syncing mechanism via writes into the client database and an elaborate allow/deny mechanism, but in practice most people use the following simple workflow:

Meteor also provides a method-call-mechanism by which a client can call the server to do (or fetch) stuff. So that's basically RPC in a very simple but powerful format.

These methods also allow for "client side simulations", optimistic updates to the client side database, with the changes getting rolled back / updated once the server part of the method has done it's updating of the database.

So the workflow for working & updating data in the DB looks like this:

- Data is "canonical" on the server DB

- Client subscribes for the necessary data for its client side cache

- When the user triggers an action, the client calls a method on the server, eg: "likePost(post_id)"

    - The client side simulation can actually increase the like count on the "Post" document in the local minimongo database

    - The server then executes the method & increments the like count in its database, if the request is valid

- The client syncs its database after the method has completed to make sure its optimistic update lead to the same results as the server call did on the server.

- The client updates its UI always reactively as soon as the data in its local db has changed.

All of this is very performant as long as you keep it cool and subscribe only what's actually needed for the current view,

Oh, and all of this has fine grained reactivity, on the client. The whole solution is really powerful, while deceptively simple.

Having the same API on both client and server allows for "isometric" code, meaning code which runs on both the client and the server, so you don't have to have two different versions of helper code, which is really cool too.

Meteor.js is pretty much a bit like "the old PHP experience" to me: As a full Stack developer I can write powerful apps with only one codebase which is shared in parts between client and server.

Link to Pub/Sub docs: https://docs.meteor.com/api/pubsub Link to the Method docs: https://docs.meteor.com/api/methods

danman114

2 năm trướcdiscuss

Simple Question: how could I as a private party contribute to help this get more friction & ultimately more success?

comments