Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

WebStorm and Rider Are Now Free for Non-Commercial Use

blog.jetbrains.com

Post reply on HN
Print view View original

21–30 of 64 posts

Re: WebStorm and Rider Are Now Free for Non-Commercial Use

#21

Post by jasonlotito »

OutOfHere wrote: post #13
simion314 wrote: post #11

Earlier quoted context omitted.

>Secondly, the free JetBrains IDEs also lack devcontainer support which is readily present in VSCode. To not use devcontainer is a substantial security hazard. Can you elaborate? Is VS Code making containers for you so you are safe from packages or from random plugins you have to install?

Why do I have to elaborate? It is well known that a container offers a sandbox and process isolation. The risk from not using one can be severe. The risks include but are not limited to packages and plugins.

> Why do I have to elaborate?

It's well known that the comments on HN are great for having discussions. You don't have to participate, despite your belief that you are required to. But, it's well known that having a discussion is a two way street, with people commenting and asking questions, and people replying.

Re: WebStorm and Rider Are Now Free for Non-Commercial Use

#22

Post by arkh »

sitkack wrote: post #17
TYPE_FASTER wrote: post #9

Earlier quoted context omitted.

Same here. The JetBrains products are indispensable for me. They've converted me after being an Emacs user for 30 years.

Can you imagine if JetBrains worked their magic on Emacs?! Years ago, there was a company that made a refactoring engine for C, I believe I paid >100$ for it in the late 90s or early 2000s. It was a standalone server that could communicate with Emacs (I wasn't an Emacs user). For a consulting engagement, I bought this tool and learned Emacs. I printed out a poster that I put on the wall that show the workflow for the…

> Can you imagine if JetBrains worked their magic on Emacs?!

No need for a mouse and on-the-fly macro recording and replaying? How many first-born do they want?

Re: WebStorm and Rider Are Now Free for Non-Commercial Use

#23

Post by OutOfHere »

lolinder wrote: post #16
OutOfHere wrote: post #13

Earlier quoted context omitted.

Why do I have to elaborate? It is well known that a container offers a sandbox and process isolation. The risk from not using one can be severe. The risks include but are not limited to packages and plugins.

> Why do I have to elaborate? Because some of us have never heard of devcontainers as a named concept with its own spec until now. I've been running my dev servers inside containers for a long time now (using JetBrains IDEs!), but have never heard of this before. > It is well known that a container offers a sandbox and process isolation. No, actually, it's well known that containers don't do that. It's one of the fir…

> security isn't one of them

Oh but it is. If there is harmful data-stealing software running in the container, it will remain isolated to the container. And if the kernel is shared with the host, that's a read-only share.

Re: WebStorm and Rider Are Now Free for Non-Commercial Use

#24

Post by OutOfHere »

simion314 wrote: post #14
OutOfHere wrote: post #13

Earlier quoted context omitted.

Why do I have to elaborate? It is well known that a container offers a sandbox and process isolation. The risk from not using one can be severe. The risks include but are not limited to packages and plugins.

So you are afraid of evil packages but then you deploy them in production? So you are safe and screw your users ?

Huh. That makes no sense. If I am experimenting with something, I won't necessarily deploy it.

Re: WebStorm and Rider Are Now Free for Non-Commercial Use

#25

Post by OutOfHere »

jasonlotito wrote: post #21
OutOfHere wrote: post #13

Earlier quoted context omitted.

Why do I have to elaborate? It is well known that a container offers a sandbox and process isolation. The risk from not using one can be severe. The risks include but are not limited to packages and plugins.

> Why do I have to elaborate? It's well known that the comments on HN are great for having discussions. You don't have to participate, despite your belief that you are required to. But, it's well known that having a discussion is a two way street, with people commenting and asking questions, and people replying.

[flagged]

Re: WebStorm and Rider Are Now Free for Non-Commercial Use

#26

Post by scblzn »

However, be careful with the terms of non-commercial usage (Enforced heavy metrics)

"You agree that the product will send usage data to validate your compliance with the license terms and anonymous feature usage statistics..."

"The information collected under Sections 4.1. and 4.2. may include but is not limited to frameworks, file templates used in the Product, actions invoked, and other interactions with the Product’s features."

Re: WebStorm and Rider Are Now Free for Non-Commercial Use

#27

Post by fragmede »

OutOfHere wrote: post #23
lolinder wrote: post #16

Earlier quoted context omitted.

> Why do I have to elaborate? Because some of us have never heard of devcontainers as a named concept with its own spec until now. I've been running my dev servers inside containers for a long time now (using JetBrains IDEs!), but have never heard of this before. > It is well known that a container offers a sandbox and process isolation. No, actually, it's well known that containers don't do that. It's one of the fir…

> security isn't one of them Oh but it is. If there is harmful data-stealing software running in the container, it will remain isolated to the container. And if the kernel is shared with the host, that's a read-only share.

> remain isolated to the container.

Assuming the code that implements the containerization is 100% bug free and there are no container escapes. I would not bet my user's safety purely on that assumption.

Re: WebStorm and Rider Are Now Free for Non-Commercial Use

#28

Post by lolinder »

OutOfHere wrote: post #23
lolinder wrote: post #16

Earlier quoted context omitted.

> Why do I have to elaborate? Because some of us have never heard of devcontainers as a named concept with its own spec until now. I've been running my dev servers inside containers for a long time now (using JetBrains IDEs!), but have never heard of this before. > It is well known that a container offers a sandbox and process isolation. No, actually, it's well known that containers don't do that. It's one of the fir…

> security isn't one of them Oh but it is. If there is harmful data-stealing software running in the container, it will remain isolated to the container. And if the kernel is shared with the host, that's a read-only share.

I think you're missing my point: you are saying that it is one of the benefits, but they don't because it isn't one. Containers are not a security solution for running untrusted code. You saying they are does not make it so.

> And if the kernel is shared with the host, that's a read-only share.

No, it's not, the kernel is reading and writing files constantly for the container. A bug in the kernel could be exploited to break the sandbox, which isn't possible in a true VM.

Re: WebStorm and Rider Are Now Free for Non-Commercial Use

#29

Post by appplication »

abhijeetpbodas wrote: post #3

Specifically worth noting: > It’s important to note that, if you’re using a non-commercial license, you cannot opt out of the collection of anonymous usage statistics.

This is a common and acceptable tradeoff for free products.

Re: WebStorm and Rider Are Now Free for Non-Commercial Use

#30

Post by appplication »

OutOfHere wrote: post #10

JetBrains IDEs are better than VSCode, but due to Copilot integration in VSCode, I moved away from JetBrains. I don't see myself going back to JetBrains. Secondly, the free JetBrains IDEs also lack devcontainer support which is readily present in VSCode. To not use devcontainer is a substantial security hazard.

I used to think containers were they way and maybe they are, but so far my experiences with them has been really poor and marked by confusing interfaces and unnecessary GUI ops vs e.g. git ops.

If someone could explain to me how to programmatically perform all lifecycle features with a container (e.g. rebuild etc) without ever having to touch VSC’s special in-IDE command palette that would be incredible.

The current iteration is too much magic at the expense of too little control and visibility.

Post reply on HN