●Stories
●Firehose
●All
●Popular
●Polls
●Software
●Thought Leadership
Submit
●
Login
●or
●
Sign up
●Topics:
●Devices
●Build
●Entertainment
●Technology
●Open Source
●Science
●YRO
●Follow us:
●RSS
●Facebook
●LinkedIn
●Twitter
●
Youtube
●
Mastodon
●Bluesky
Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!
Forgot your password?
Close
This discussion has been archived.
No new comments can be posted.
Load 500 More Comments
Full
Abbreviated
Hidden
/Sea
Score:
5
4
3
2
1
0
-1
More
Login
Forgot your password?
Close
Close
Log In/Create an Account
●
All
●
Insightful
●
Informative
●
Interesting
●
Funny
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
byDarkness404 ( 1287218 ) writes:
Seriously Google how hard can it be? Just use GTK, its light, useful and even a weekend coder can use it.
byTinBromide ( 921574 ) writes:
Yeah, that and the lack of a "unified and comprehensive HIG" seems a little dishonest for a company that created a windows browser that looks NOTHING like any other piece of windows software, follows its own interface methods, and generally throws off the look and feel of the browsing experince. While i'm aware that a HIG should cover more than just the look and feel, it feels like google bends the rules when it comes to interface guidelines.
byCarpetShark ( 865376 ) writes:
They certainly did break the windows HIG. Then again, I'm a big fan of standards, and yet I've deliberately broken HIGs when I knew they didn't apply well to a new kind of application. I feel justified in doing that, since I've been around since the basically the dawn of GUIs and been able to slowly watch the standardisation process of most widget types. None of that means that I want to start from scratch on a platform though, without any standard HIG already in place. It's one thing breaking the HIG when necessary. It's quite another if no one has bothered to agree on the HIG necessary for even the most typical apps.
Anyway... google are quite right here, I think. When are Linux standards people going to wake up and realise that ANY good, standardised library is better than two that are both great? Especially in open source, the fact that it's a standard allows people to focus on improving it. The whole point of an API is to have something to target your software to. It's also a standard which can be evolved later, even if the next version is as different as Qt is from GTK+. I don't give a crap if the standard is Qt or GTK+ --- whichever is chosen will eventually gain the features necessary for modern apps --- but SOME standard needs to be set.
Parent
twitter
facebook
bycylcyl ( 144755 ) writes:
I agree that there should definitely be consolidation
Personally, I like Java because there is a set of useful libraries (threads, tcp/ip, etc) that you can rely on being there
As opposed to C/C++, where even POSIX compliant libraries for each are not necessarily compatible. Wasting developer / designer time on evaluating utility library instead of business logic
byCeleste R ( 1002377 ) writes:
Agreed. However, Windows allows you to break the HIG fairly easily. You can't do it so easily in Linux (try having Compiz or Metacity or KWin agree on a way to cleanly extend those tabs into the title bar).
I remember that Windows has been able to do that since the Windows 3.1. I forget exactly which piece of software I saw do it first, but the functionality was there. It's probably legacy code that MS drew up to support changing a UI that they weren't completely sure about.
And as we all know, Microsoft
byadamjaskie ( 310474 ) writes:
There's nothing stopping someone from setting up a "standards body" and trying to dictate what libs should and should not be used. All they have to do is get a few major distros on board, and convince people that's the way to go. Simple.
byHermMunster ( 972336 ) writes:
That's the worst thing that could happen to open source. Open source allows fast evolution and forcing standards done by someone else isn't a solid solution.
His solution, the google employee, is to rise above it and get it working. He's a complainer. He can't do hard work without complaining first, in the middle, and at the end.
There are enough standards that he can do everything he needs and to make it a real Linux program. Sounds to me like they really messed up the internals and the interface that the
●nt threshold.
●reshold.
There may be more comments in this discussion. Without JavaScript enabled, you might want to turn on Classic Discussion System in your preferences instead.
Slashdot
●
●
Submit Story
It is much harder to find a job than to keep one.
●FAQ
●Story Archive
●Hall of Fame
●Advertising
●Terms
●Privacy Statement
●About
●Feedback
●Mobile View
●Blog
Do Not Sell or Share My Personal Information
Copyright © 2026 Slashdot Media. All Rights Reserved.
×
Close
Working...
Working...