Hacker News new | past | comments | ask | show | jobs | submit | krstf13's comments login

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.


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 )


thanks for the detailed answer of the differences. The interactive (I assume using CRDT's) is a good feature, jupyter server does not have this and is at a time a bit of a hassle. Also deploying it directly as an app is pretty sweet.


Livebook actually uses state reducers as described here[1]. Except for cell content. There it uses Operational Transformation. The source code[2] is really instructional and easy to understand. I highly recommend to look into it :)

[1] https://github.com/jonatanklosko/notebooks/blob/main/article... [2] https://github.com/livebook-dev/livebook/blob/main/lib/liveb...


A great read, thanks so much!


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.



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)


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.


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


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.


This is, so far, an excellent write up. The motivation section is great, it’s clear, acknowledges that the C version is probably fine and simply states the authors wanted to gain more insights into the process of porting C code. If the rest of this series is half as good as this instalment, I’m eager and excited to read it. A real breath of fresh air. Thank you.


To add to what the parent wrote, depending on your situation (eg unemployment) when your creating your micro-company, you get a grace period (up to 2 years, I believe) during which your fees are substantially reduced. And the fees include social security, with (since recently) roughly the same benefits as regular employees (except for compensation of lost revenues in case of illness, which is more complicated).


This is grossly inaccurate. What you're calling taxes, are fees that allow employee to get several benefits. Practically speaking, these are delayed salary.

They include social security, unemployment benefits, retirement benefits, training ...

When your employee is sick, they can stay at home without losing their pay, and without your company paying for it. They can seek medical treatment without risking bankruptcy.

If you have to lower you activity because business is bad, you can put in place part time unemployment, and your employees won't lose money in the process...

Also, the fees paid by the employer are often subsidised through eg tax credits, reimbursements (up to a certain amount)... So that these numbers are not only inaccurate but also totally meaningless.


French has multiple words historically (impots, taxes, charges) with subtle differences in meaning. However they've not been observed strictly in a long long time. It's all money taken out of the employee pocket at the end of the day.

In English it's all translated to "tax" and rightfully so. English languages and cultures don't have subtle semantics like French does. For example everything in the UK is a tax, corporation tax, income tax, council tax, etc... (one exception being the UK national insurance).


Same in the US. On my paycheck there are Social Security tax, Medicare tax, State disability insurance tax, State unemployment insurance tax. If it is a mandatory deduction taken out of your paycheck to fund a government project (not the best word, but can't think of the proper word at the moment), even if you get benefits later, it's called a tax.


The US Government tries the same trick.

Social Security is a called an "insurance program" although it is completely unrelated to conventional insurance. The closest financial instrument is a Ponzi scheme, which is illegal under US law.


It is insurance in the sense that it pools the risk. The risk here is "aging" ("Social Security" in the US only covers base retirement, whereas "Social Security" in France covers 5 risks), it only happens to be a risk that realizes 100% of the time, unlike fire insurance for instance.


Nope,that’s not correct. Even in English health insurance is not tax, unemployment insurance is not tax... And by the way what you call ‘charges’ is historically‘cotisations’ (fees).


In my circle of acquaintances, the distinction lies not in what the money is funding (e.g. health care), but in where it's going:

Health coverage goes to some entity that isn't the government and is usually optional, so it's viewed as a benefit and taken into account when computing total compensation.

Unemployment insurance on the other hand is taken out of every paycheck and handed to the government without an opt-out. Yes, of course you get something for it; the whole point of taxes is that society gets something in return. They're still taxes.


Also, you lie and move the goal posts. You really should say that you don’t wanna pay your employees. Fine by me, but be frank about it. I know I’ll be downvoted here, but the truth is this guy doesn’t want to pay his employees and pretends it’s because of additional costs that burden him. He’d rather give them more, if only they were able to spend responsibly. Yet, he doesn’t know the first thing about taxes, fees and lumps them together. I welcome disagreements, but I wish un readers were slightly more rigorous.


I don't get that impression at all. The person you're replying to hasn't done anything more than try to clarify that whatever you want to call the cash being extracted by the French government, a reasonable person in other parts of the world could call it a tax and not miss any important defining characteristics.

With respect to claims of wanting to underpay employees, I don't think that's something anyone is actually arguing for when they talk about unfriendliness toward startups. The French government is levying a high _proportional_ tax to cover _fixed_ fees like health care. This can make sense at a societal level as a form of wealth redistribution, but it's a disadvantage for high earners like those in the software industry. Those employees can earn more in other countries with the same cost to their employers simply because less is taken out of their paycheck, and because the difference is more than enough to cover fixed fees like health care it's a good move for them to do so. The people being disadvantaged aren't startup employees (not passing a moral judgement -- the claim itself just seemed off).


I think quibbling about terminology misses the point. If you think about it as the total cost per employee, it seems like a a lot that doesn't actually go directly to the employee as take-home pay. I think a lot of that is good, and replaces other external costs, but it's still a lot of extra money a small company will need to budget just to hire someone.

And things like tax credits are only useful if you have the cash on hand immediately, and can wait up to a year to get it back. A brand-new venture may not have that.


All of this is called "tax" in the US.


Not quite: health insurance is not called tax in the US, yet is a benefit under the French system with premiums paid by the employer.


Not quite: An employer in France must provide a private health insurance plan to employees. It is paid out of the pocket of the employee and they can't refuse it.

France has good public health service but it's also pushing private health insurance down the throat of everybody through their employers, quite like the UK or the US. The large majority of the population has double coverage.


This can’t be for real and isn’t.

It is illegal to try to criticise a court decision in a way that is designed to impede the justice system and/or to interfere with the independence of the judiciary.


I am not a lawyer but as far as I am aware it is illegal to say publicly for instance that a court decision was politically motivated. You might argue that it would undermine the justice system but this is 100% in lack of accountability territory.


You can say publicly that a court decision was politically motivated. What matters is how it is said and somewhat by whom (a member of the government might be held to higher standards).


>What matters is how it is said and somewhat by whom

That means you can't say it. You might be able to say it, depending on who you upset.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: