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

JetBrains Web UI components open-sourced

blog.jetbrains.com

Post reply on HN
Print view View original

91–96 of 96 posts

Re: JetBrains Web UI components open-sourced

#91

Post by scierama »

true_religion wrote: post #87
chii wrote: post #86

Earlier quoted context omitted.

if enough people call out the lack of accessibility in UI libraries, it brings that requirement into the cultural norm. The commenter is merely trying to push this into the cultural norm. I concur with such sentiments.

I think there are better times to do this than the initial version 0 release of an open source production. Taking the chance to "call out" its "lack", is essentially shaming people for doing social good (open source), and not going far enough in someone's opinion.

You can think what you want. The people who downvoted me for simply asking why the parent was downvoted can think what they want. The mods can think what they want. It doesn't justify anyone for downvoting the parent's comment which was his view or mine for calling out the unjustified downvoting. This is where the mods should step in, find out who was downvoting both the parent and me; and remove their ability to downvote for a time.

Re: JetBrains Web UI components open-sourced

#92

Post by tvararu »

true_religion wrote: post #87
chii wrote: post #86

Earlier quoted context omitted.

if enough people call out the lack of accessibility in UI libraries, it brings that requirement into the cultural norm. The commenter is merely trying to push this into the cultural norm. I concur with such sentiments.

I think there are better times to do this than the initial version 0 release of an open source production. Taking the chance to "call out" its "lack", is essentially shaming people for doing social good (open source), and not going far enough in someone's opinion.

Tacking on accessibility at the end is very difficult (most of the time it's quicker to rewrite). By not considering it from the beginning it means these components will never be usable by people with access needs.

Also it is possible to call out a critical oversight in the design of a product while not shaming them for releasing it.

Re: JetBrains Web UI components open-sourced

#93

Post by davkean »

louthy wrote: post #76
jedwardhawkins wrote: post #75

Earlier quoted context omitted.

Your experience with VS and your desires for Rider reflect my own. Correct me if I'm wrong, but isn't Visual Studio still a 32 bit application? That would definitely limit the utility of those 128GB.

I tend to have a number of solutions open. But mostly I was just trying to convey that my setup isn't to blame (fastest possible ram, large amounts of it, super fast cpu, all off SSDs too). Obviously a 32bit app could run a number of sub app domains, so it can still make use of more than 2gb. I think ultimately though is it's not the resource that's the issue, it's the buggyness of the system. It just feels unfinishe…

louthy, I'm from the VS team. Sorry to hear that you are running into this. Can you Help -> Send Feedback - Report a Problem (don't worry about the contents), and point me to the resulting feedback? I'll dig into your performance data and make sure we've got bugs/fixes for the things you are running into.

Dave twitter.com/davkean

Re: JetBrains Web UI components open-sourced

#96

Post by orangy »

rufugee wrote: post #60
adamnemecek wrote: post #15

JetBrains is kinda crushing it. I've spent the last two days looking into Kotlin. I didn't realize not only that Kotlin can compile to JS but also that you can interact with say React from it. So you can build a full stack app in it, without ever touching JS. (I think that the JS compilation is still technically in beta but w/e). https://github.com/Kotlin/kotlin-fullstack-sample Combined with the fact that you can us…

I was coincidentally looking at Ktor yesterday. I quickly ran into pages which are linked from the Getting Started guide (such at http://ktor.io/Features ) which don't exist. Doesn't give the best first impression, but I gather it's a very new framework so I'm sure it'll be corrected soon...

We are sorry for broken links, we just recently migrated from GitHub wiki pages to own site and indeed some links could've migrated incorrectly. Thanks for the heads up, we will fix it :)
Post reply on HN