The chats, calendars and CI/CD into one is top for our team. Really can help us stop using multiple tabs and tools
Jetbrains Space
91–100 of 104 posts
Re: Jetbrains Space
#92We use Space due to GitLab's recent pricing changes. We like: - free git hosting - free slack-like with sub-thread - generous CI/CD - built-in issue tracker - built-in wiki - very snappy - has mobile app We don't like: - CI/CD script uses Kotlin DSL, feels "heavy". - Issue tracker very basic, we end up using YouTrack. Still don't know how to integrate it lol. - One project can have multiple repos, but they all share…
> - CI/CD script uses Kotlin DSL, feels "heavy".
That's a PRO!
Every CI/CD tool that uses yaml or any other non-programming-language should burn in hell.
Let the developer write the code that creates the datastructure that describes the CICD process. That is flexible, reusable and can even be made typesafe.
Re: Jetbrains Space
#93Earlier quoted context omitted.
vs code could always go this way in the future too. some of their most popular features are closed sourced freeware. they probably would never directly charge but it definitely violates the open source spirit when the guts of your IDE are closed off
The out of the box experience of Pycharm is just amazing. Agreed you can do all this with VScodium or even Vim but it's all so much setup...
Also, the depth of the inspections present in all of the JetBrains products make them absolutely incomparable to any "linter" setup or current LSP implementations. But, relevant to this topic, so too is it some unholy incantations to try and run those same inspections in CI, partially because I think that very concept isn't important to JetBrains and partially because of the indexing required by the JB IDEs that drive everyone starkraving mad as compared to the less intelligent editors that can load a text file in a super big hurry
Re: Jetbrains Space
#94Jetbrains is so good, it scares me they’ll become the next microsoft.
In my experience, no one is forced to use JetBrains, but there are innumerable work setups that mandate Windows and thus a lot of the Microsoft tooling that implies
It's also hard to distinguish from outside of that ecosystem how much Microsoft is pretending to play developer advocate in pursuit of the infamous E.E.E. strategy versus PR damage control versus they really do want to ship good dev tooling. I bring that up because if one is afraid of JetBrains morphing into Microsoft, that question brings up "what is Microsoft's motivation" in order to compare how much JetBrains would, or aims to, have those same motivations.
I'm thrilled out of my mind to pay JetBrains the $whatever/year they ask of me because I unquestionably get that much value out of them. And that's not even counting the amount of benefit I get from being able to fix bugs in IJ Community and PyCharm Community due to them being Open. That leads me to believe JetBrains Browser, JetBrains Office, and JetBrains OS are likely quite a ways off because they have plenty of healthy marketshare as it is
Re: Jetbrains Space
#95Earlier quoted context omitted.
+1 having to juggle multiple IDEs for a multi language project is clunky.
Yeah, bonus points for them seeming to use the same `.idea` directory but in incompatible ways :sob:
this a big part of that-- the different ides can't even share the same root directory. it'd be 50% solved if they just used `.idename`
I'd like to share run configurations between them, which would remain unsolved by that.
Re: Jetbrains Space
#96Earlier quoted context omitted.
Yeah, bonus points for them seeming to use the same `.idea` directory but in incompatible ways :sob:
this a big part of that-- the different ides can't even share the same root directory. it'd be 50% solved if they just used `.idename` I'd like to share run configurations between them, which would remain unsolved by that.
That run configuration one I'd guess is only partially true, since the recent ones write them to `.run/foo.xml` versus the old style `.idea/runConfiguration/foo.xml`. I haven't dug into it in order to know if the structure of the IJ xml versus the PyC .xml etc differs, but I'd guess they're a lot more likely to share code than the teams that write the Project persistence
Re: Jetbrains Space
#97Earlier quoted context omitted.
Feels like there's a big race to be the all-in-one everything tool for everything. It's Gitlabs whole schtick, GitHub is moving in that direction, now "also Jetbrains". IMO I think something like Jetbrains should be leaning into integration, not all-in-one. Connective tissue last longer than walled garden.
The race is to go back into the timesharing development workflows, under the guise of cloud development. Instead of telnet, ssh and X display, we get to use the browser.
Sure. The cloud is the new mainframe.
Mainframes were ever since the best option to milk locked-in customers, so the story continues.
The tech is different, the strategy the same: Be the all emphasizing platform so nobody can leave without needing to rebuild substantial parts of their business form the ground up.
Replacing the mainframe after been invested in it constitutes for many a mayor headache to this day. So one can conclude that the said strategy works well since decades.
But that's no news, is it?
Re: Jetbrains Space
#98I've canceled my Jetbrains subscription this year after about 10 years. While Goland is gold, Webstorm was a constant source of issues and annoyances. VS Code is light years ahead in the JS world supporting Vue (Volar), Svelte, Tailwind - to name a few. In Webstorm, essential bugs / missing feature are open for years. Fixing Tailwind support took ages - no idea if it's working properly now.
After switching to VS Code I found that almost everything you get with Jetbrains IDEs is available (often better) as a VS Code extension. The only area where Jetbrain has an edge is their integration with DataGrip, which is brilliant. But then, turned out DataGrip doesn't support the recent SQLite version. The answer from the Jetbrains support was a link to an open source repo that was not maintained anymore (or for a period of time - who knows). That's what I go after paying for 10 years for their ultimate package.
Now I'm a more than happy VS Code user. The only thing I really miss is DataGrip.
Instead of fixing their core products, they're creating new ones like Space. That is of course legitimate. They have all the right in the world trying to make more money. But it won't be my money.
Re: Jetbrains Space
#99I don't use any Jetbrains product and I have no idea how well-executed this is, but I am pleased to see a relatively smaller company competing against the almost monopoly of Microsoft's VS Code and GitHub.
It's interesting to read this, because from my stats just a few people are using VS Code - most of them use IntelliJ-based IDEs or Vim. I’m a freelancer, so I’ve been working with teammates from many countries, from every continent.
Re: Jetbrains Space
#100Earlier quoted context omitted.
Heh. You know who made their fortune providing "everything else handled by default"? Microsoft. Now that enters a fairly divisive terrain, but needless to say, what you expect from single source of tooling generally does not end up being delivered.
I hear you, and I'm certainly not after Conglomerate Enterprise Tooling. But I think there's room for somewhere between that and makeshift tooling pipelines. Not everyone has to use it, but I'd like to have the option of an integrated software development platform.
Withcoherence.com is one new option (I’m a cofounder). Would love your thoughts if you get a chance to check it out - hn@withcoherence.com…