HN user

jarek83

375 karma
Posts1
Comments196
View on HN

As others commented already - the author does not seem to understand principal idea behind running a business - a company is not something "yours", because you can just simply sell your shares or be moved out from the company by other partners.

Company is a state's legal entity given to designated people to manage (the forming person/partners) and profit from doing it successfully. If those people fail they have to follow strict rules (liquidation) or they will be sued personally for misconduct. That entity gives much more possibilities because it is limited liability - part of which is held by the state, and part by the running founders.

If you want something yours, you go with the sole proprietorship.

We tried to ship company-provided laptop from Poland to somewhere in India. After long time the parcel was just simply labelled "gone". And we paid very similar amounts for all the shipping/taxes/clearances. Nice to hear that such stories end well sometimes.

I must as intelligent as you because I also never understood why things like supabase even exist. I believe this shows how much front-end dev world is detached from how things can simple and secure by default.

I wonder if AI labs could be bailed out - like banks.

See, they kind of became a national asset and letting it go down, will leave USA watching China taking the lead for a very long time ahead. It just can't happen - right? So we'll just all fund it in taxes.

BMW's most recent infotainment is a big step backwards to me in both areas - aesthetics and UX. Its previous generation was one of the best in the market also in both. I literally don't consider buying the newest 4-series just because of it, especially of the ultrawide driver's "monitor" - it's just so ugly, and I regret it, since on the outside the car appeals me so much more. I'd rather spend the same on previous year model with better specs.

So this happened only because google is so big, that it can point to any website and say that it's not safe. Even if owner of a site just don't want to be in their search engine in the first place.

How on earth we ended up with this company bother anyone including those that want their services? Imagine that you could get your driving license banned because you did not buy a toyota...

I think the benefits of either clean code (sepearate methods) and commenting "what" are of different kind:

- clean code one, for me it just reads easier, specific bits of the larger operation are not surrounded with noise coming from other bits like it is in the commenting "what" one. I can focus more on each step, and that can make it easier to spot a bug or to refactor/adjust/extend, as now I'm more like on a given page of Lego set instructions

- the commenting of "what" one - yeah, this obviously makes it quicker (but probably not easier) to see the larger picture. It has benefits, but I believe this helps more hacker/scripter kind of people than programmers

It could be done with :indeterminate state (so key in a cookie would be absent or removed when switching), but I'd probably would do it with radios instead

Sure:

- images: none are visible above the fold - all should be lazy loaded (like it is done with all conference images) and the pragdave.jpeg one does not need to be that large;

- JS: navigation toggle, including chevron rotation can be done in CSS using :has combined with checkbox/radio input. Similarly for header-navigation and theme-toggle (here combined with cookie store). Then toc.js - seems like something easy to do in the backend. Hero-animation - I haven't looked much through it but seems like at least some parts can be done in CSS;

- CSS/tailwind - well it would probably take less typing to do it just in CSS, the site does not seem to be that much componentized to benefit from tailwind.

I like how it looks. I don't like to see how badly it is crafted tech-wise - not optimized images by size and deferring, JS for things that work natively in the browser, bloat of tailwind instead of nice clean and modern CSS.

Knowing ruby I can tell that the relaxed approach to the website does not correspond with sophistication in the language itself. If I wouldn't know ruby, that would be a put off for me, thinking that if they don't want to convince me tech-wise by their site, it might be similarly annoying to deep-dive into the language.

That's exactly the use case I would go too (since I'm not native English) and while we have a technology now for this, people will straight away reject because LLM. Funny how we always wanted to connect the world and know it is just not compatible with the situation.

Just use a button 9 months ago

It's a thing from the times when <button> did not exist. Other use cases were for supporting IE. Today just use button.

Just use a button 9 months ago

The type of developers that would go with <div> in such cases are also those that know very, extremely little about semantic HTML and its purpose. Then if one is challenged about using React or other heavy-JS framework when you don't really have to, the discussion will be met with utter even surprise that someone out there is actually not using React.

The web is darn simple, but we are the place where it is made extremely over engineered and expensive for both companies (salaries and 2-3x more staff needed than necessary because of the bloat) and users of their products (in terms of payloads).

And yet JS-heavy frameworks seems to have the best job market.

Everything seems to be upside down.