Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
mrdoops
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
9 ms
·
31.
▲
by
mrdoops
4y ago
From my own experience in the Elixir community watching libraries develop the non-blocking preemptive actor-model concurrency is a good default for most situations. Dropping into things like Rust NIFs has been great for those hands on situa
32.
▲
by
mrdoops
4y ago
Phoenix Liveview and the many other copied featuresets in other web frameworks are sending dom diffs over a websocket connection where a tool like morphdom will render only the necessary changes to the page. This sort of architecture for st
33.
▲
by
mrdoops
4y ago
(Worked in the residential solar industry on and off almost 10 years) Financing providers, sales commissions, and profit + operating margins of the typical end-to-end residential solar sales and installation company make up a large portion
34.
▲
by
mrdoops
4y ago
Serverless systems in almost every implementation are still stateless or limited stateful-serverless (the best examples are probably Microsoft's Durable Functions or Flink's Stateful Functions - there's also solid attempts by
35.
▲
by
mrdoops
4y ago
For I/O, concurrency, fault tolerance, and distribution it really doesn't get better than the BEAM, but when problems get CPU intensive you can't beat C/C++/Rust. So this idea of using pre-compiled Rust NIFs from El
36.
▲
by
mrdoops
5y ago
Elixir. That's it. There's a reason Discord and WhatsApp run on the BEAM. It does real-time with the least pain.
37.
▲
by
mrdoops
5y ago
Definitely a cool piece of software - there is a lot of unsurfaced potential in distributed graph databases - good luck I hope the future is bright.
38.
▲
by
mrdoops
5y ago
In a backwards way this validates the general decentralization movement crypto is a part of even more in that a mob attack on social media can get an organization like Mozilla to limit their own capacity to accept donations.
39.
▲
by
mrdoops
5y ago
Neat thing about Luerl is that you can manage many isolated Luerl vms from within an Erlang supervision model which is a very desirable trait for things like games with user defined scripts that may explode.
40.
▲
by
mrdoops
5y ago
Yeah offline or complex client side state management is a good use case for Javascript. There are Hooks and Push Events with Liveview for real time integrations with Liveview in those scenarios. In my experience offline requirements are rar
41.
▲
by
mrdoops
5y ago
React might make sense for some specific components wired up with hooks in Liveview for real-time interactions. So if you have a complex client side component that is already available in React and you don't want to recreate it - I
42.
▲
by
mrdoops
5y ago
Elixir is modern tooling on top of the BEAM / Erlang Virtual Machine. This is tech that has been running Telecom systems, companies like Whatsapp, Discord, Klarna, and software like RabbitMQ, etc for decades. The core libraries are ver
43.
▲
by
mrdoops
5y ago
Phoenix + Liveview + TailwindCSS + Postgres Unless a static site or buy option fits right, otherwise it doesn't get any better than a Liveview based app for continued productivity.
44.
▲
by
mrdoops
5y ago
Yep and this approach also allows languages like Julia and Elixir to compile their expressions into valid compute graphs that target JAX/XLA. That polyglot capability opens up cutting edge machine learning into quite a bit more ecosyst
45.
▲
by
mrdoops
5y ago
For getting the business off the ground - there's often a build vs buy question. My rule of thumb is buy for generic build for core. For SaaS/web app aspects? For me, probably a flavor of the PETAL stack i.e. Postgres/MySQL +
46.
▲
by
mrdoops
5y ago
They need stable, actionable futures. Homes they can afford to own, communities they can raise kids in, an environment that won't go up in flames; they need systems that have their back.
47.
▲
by
mrdoops
5y ago
Build something better.
48.
▲
by
mrdoops
5y ago
More demand -> increased prices for developer time. Greater costs / impact / scale of software development -> greater risk to the collective stakeholders. Greater risk -> more potential for reactionary measures to impleme
49.
▲
by
mrdoops
5y ago
Want to build a real time chat app? Best build it on the BEAM.
50.
▲
by
mrdoops
5y ago
Agreed. I would bet on a language like Elixir or F# being simpler to learn and grow for a complex system than a class-oriented-imperative-oop (Java, Ruby, Python, etc) language any day.
51.
▲
by
mrdoops
5y ago
Are there plans to implement a distributed stream messaging system (e.g. Kafka, RMQ streams) embeddable in a supervision tree like Phoenix PubSub? Way easier said than done I'm sure, but I know personally there are a lot of use cases f
52.
▲
by
mrdoops
5y ago
They're also separating out Phoenix.View so there will be less dependencies on using Phoenix view rendered templates for things like email or PDF generation outside of a web layer.
53.
▲
by
mrdoops
5y ago
The whole approach of regulating on the level of "please don't exploit vulnerable systems" seems reactive to me. If the cats out of the bag on a vulnerability and it's just data to copy and proliferate - not much a gover
54.
▲
by
mrdoops
5y ago
I expect streaming will be adopted like anything - first in smaller more mobile teams working in greenfield contexts, then later in large organizations when the idea is less novel and lower risk/cost to apply at scale. Regardless I fee
55.
▲
by
mrdoops
5y ago
I think that's a bit of a reduction/straw man to say they need a lot of architecture/central-planning. An individual developer can do it so long as they have access to domain experts to ask the right questions. Lack of proper
56.
▲
by
mrdoops
5y ago
From a technical perspective there are plenty of ways to serialize / order some stream of events in a reasonable way. Whether that's implementing your event store on top of a transactionally secure database (e.g. Postgres, not Mon
57.
▲
by
mrdoops
5y ago
A lot of comments not sure about what Graph DBs are good for: * Flexible knowledge association i.e. Knowledge Graphing * Modeling and querying associations / models with many-steps-removed requirements * Expert Systems / Inference
58.
▲
by
mrdoops
5y ago
No-code tooling or not someone still has to design the workflow. Designing a workflow requires asking good questions, which requires putting in the time with domain experts who aren't necessarily an expert in implementing a workflow wi
59.
▲
by
mrdoops
5y ago
Already planning on running this in an internal cluster for training & documentation scenarios. Hexdocs are great, but having a live executable tutorial connected to a staging database sounds really valuable for getting new team members
60.
▲
by
mrdoops
6y ago
OTP is definitely more of an expert's toolset than a framework for throwing together features quickly. This is a good thing because it's not trying to be more of an abstraction than necessary. With OTP you can make fault-tolerant,
More ›