krstf13 · HackerTrans

3 ปีที่แล้วdiscuss

Not to be rude. The live playground probably can’t run elixir/erlang code. And it most certainly cannot connect to a remote running node instance. It’s unfortunate, that the angle here is documentation since, while Livebooks are great for testing and documentation ( https://blog.appsignal.com/2022/05/24/livebook-for-elixir-ju... ), they also provide a great environment for experimenting with elixir code. I’m sure docausorus is great, I’m not sure why you would think Livebooks would be a competitor in the same space. As to you asking for in production links, I’d encourage you to install it and test it for yourself.

krstf13

3 ปีที่แล้วdiscuss

While Livebook will mostly have an appeal for people already working with erlang/elixir, it does have a few features that are pretty nice.

- it’s collaborative (think Google docs for code) when several people are working on the same instance of a livebook;

- it’s easy to extend with so-called smart cells (which are essentially pieces of gui you can inject in your document https://news.livebook.dev/v0.6-automate-and-learn-with-smart... ). Smart cells are available for various tasks (db connection/ interaction, data frame exploration, ML tasks, maps), and building your own is relatively easy;

- you can turn a notebook into a web app ( https://news.livebook.dev/deploy-notebooks-as-apps-quality-o... )

- you can run your code an a remote elixir node by attaching to it (although this requires some knowledge of distributed elixir/erlang )

krstf13

3 ปีที่แล้วdiscuss

So? Laravel uses type hinting, ok.

This has absolutely nothing to do with your previous post grossly misrepresenting a talk. You hadn’t even mentioned Laravel in it.

Type hinting is not equivalent to a static type system, which is what the parent was asking about.

Finally, in either cases, it changes nothing to the fact that the pain points mentioned in the talk were not caused by the lack of a static type system (which is not to say it cannot cause pain points)

krstf13

3 ปีที่แล้วdiscuss

You’re misrepresenting what’s being said in this talk (the relevant part of the talk is around the 15 minute mark at : https://youtu.be/XzAupUHiryg ).

The tldr was that they had patched some of the library code without considering the ramifications of the change. At no point in the talk is it said that “switching to Phoenix was a bad idea”.

Also, none of the issues they talk about are related to the lack of static typing.

krstf13

4 ปีที่แล้วdiscuss

That’s very likely. In a past life I’ve done a bunch of auditing for m and a, apart the obvious nepotistic paid internships more often than not people thought to be unproductive were really important to the organisation. Think about payroll, legal and the likes. They’re not necessarily productive in terms of the main product, but they help reduce the legal risk for the company and insure that people in the ‘productive departments’ may stay productive. As software developers we tend to only see the number of features/fixes someone pushes to the product as the main metric of productivity, however there’s way more to running a largish company.

krstf13

4 ปีที่แล้วdiscuss

He talked about it at length at the most recent elixir conf eu : https://youtu.be/Jf5Hsa1KOc8 .But it might never materialise.

krstf13

4 ปีที่แล้วdiscuss

Wouldn’t storing the deleted data in an immutable storage, with time stamp, be much better for auditability ? I mean how could you audit deleted, restored and deleted again data with that setup? Also, while I know it’s not really accurate, I tend to understand relations as sets, it makes me uncomfortable to have soft deleted data that are neither member or not member of the set.

comments