Re:Atlassian's new terms forbid benchmarking
by ethbro on Saturday September 29, 2018 @09:22PM
(#18103980)
I always thought of Atlassian projects as inheriting all the problems of Java, exposed in UX form.
Re:Atlassian's new terms forbid benchmarking
by ex_atlassian on Saturday September 29, 2018 @11:17PM
(#18104282)
Its always the people/expertise, rarely the tool or language.
Re:Atlassian's new terms forbid benchmarking
by ethbro on Sunday September 30, 2018 @12:47PM
(#18106931)
Fair. But for purposes of language = ecosystem, I'd definitely say organizations trend to mimic language structure, and vice versa.
At least to a first order, palm-reading, internet comment approximation. ;)
Modern Java, IBM
C# .NET, Microsoft
React, Facebook
Rust, Mozilla
Re:Atlassian's new terms forbid benchmarking
by anothergoogler on Sunday September 30, 2018 @03:52PM
(#18108016)
I'm not sure what's more concerning, that you're calling React a programming language or that you're unaware that Facebook is written in PHP.
Re:Atlassian's new terms forbid benchmarking
by ethbro on Sunday September 30, 2018 @07:37PM
(#18109070)
I believe you missed the point for the trees. And for the record, I'm under no illusion that Firefox is fully written in Rust either. :p
Re:Atlassian's new terms forbid benchmarking
by beerlord on Saturday September 29, 2018 @11:53PM
(#18104374)
Why doesn't JIRA offer a native desktop app? Everyone using it is on PC, Mac or Linux right? And then a cut-down iOS (iPhone and iPad) app covers the rest?
Re:Atlassian's new terms forbid benchmarking
by ygra on Sunday September 30, 2018 @02:01AM
(#18104716)
A few colleagues use a Visual Studio extension, although that seems to be mostly handy for time-tracking and limited interaction with issues. It's also stuck in a UI that goes back to 2008, so perhaps rather fitting ;)
Oh and hamburger menus are hiding the key features you DO use every page view.