astrobe_
Joined 15 years ago
Joined 15 years ago
Granted, that's the theory.
When the demands come from a company on the basis of copyright/intellectual property (that is, exclusive broadcasting rights), one can feel less comfortable about this affair; even thought the judgement mentions that the case is backed by the ARCOM, the french authority for broadcasting, which should instead IMHO deal with a couple or two of private TV channels that are obvious vectors of fake news.
But, this is the same copyright that can protect you when you publish programs, source code, images, etc., even when you use a free and open license; the licence has meaning thanks to the copyright.
Or maybe it can; the early image generators famously did output horrific images sometimes because of their limitations, but these outputs qualify nonetheless creations.
Now the interesting thing is that it is humans who evaluate them as horrific, worthless or interesting.
Certainly AIs could pretend they have that sort of opinions and judgement, but hopefully humans will remain more interested in the opinions of other humans.
They can shift their daily schedule e.g. 30 minutes earlier and peacefully drink their coffee at home. They also should eat something at home or on their way, because hurrying in a cold morning with an empty stomach is not good. Source: personal experience. I did that for months as a student until I passed out one day in class.
If they don't like waiting for the train in the cold, they probably can find a warm place near the station, and wait there a little.
I think the only real annoyance is that each programmer/team did it with their own convention (I32, INT32, i32, int32, WORD, Word bool, BOOL, Bool, etc., etc.); standardizing helps with putting everyone on the same page more than it helps porting. It doesn't prevent people from reverse-typedef-ing standard names to local "dialectal" names, though.
But I also think that one should only rarely use raw integer types, in an ideal world; the elephant in the room is that typedef is kind of the second "billion dollars mistake" [1]. C is a weakly typed language and there's no practical way to undo it (besides transpilation), so there's double no point to leave behind raw types.
[1] For those not too familiar with C, typedef defines a "type alias", not a type: https://en.cppreference.com/cpp/language/typedef
And it always will be, because "users" is plural. It is not a defect in the design of the desktop or whatever has "too many" alternatives. The mistake would be to think that "one-desktop-fits-all".
Also, the only good reason to change things is to fix problems. Nobody's really asking for "moar modernity". Starting from design theories is plain wrong. Ask users about their problems first, and the use your design knowledge to analyse and fix them.
> Strategy is another part of UX; understanding who the target user is, and determining what they want. Deciding what is important, and what is not; what will the development team prioritize and what will it ignore? "The fastest way a UX designer can save your team time is to help you say no."
He is not talking about users but customers.
That's how FOSS works: some users find it annoying to have to place and resize their windows manually, so some of them made "tiling window managers". Many Linux DEs also had virtual desktops a million years before Windows because FOSS is made by users, for users.
[1] https://www.azlyrics.com/lyrics/slayer/fictionalreality.html
Yet the point about DSL is interesting, in particular internal/embedded DSLs [2]. I lied a little earlier, my third programming language was actually Forth. His creator said in 2001, "When you devised an application you wrote a hundred words [i.e. functions] or so that discussed the application and you used those hundred words to write a one line definition to solve the application" [3].
I've been trying to do that exactly that in other languages, make it so that the code expresses "naturally" what it does as much as possible. When you succeed, people call your code "beautiful" or "elegant" (nobody ever told me that :-) which, I think, subsumes "naturality".
This is of course harder to do in low-level languages such as the ones I mentioned (except Basic maybe) because you get caught in details such as memory management. But high-level languages are not exempt of these problems (and contrary to Forth or Lisp, their syntax is often written in stone). Then there's essential complexity [4], which can be "unnatural" no matter what, like thinking about things in a concurrent programming context, with languages that don't natively support it like they support automatic memory management (i.e. garbage collection).
The topic is dangerously close to "readability", which is known to be 80% subjective.
[1] https://www.cs.utexas.edu/~EWD/transcriptions/EWD08xx/EWD831...
[2] https://en.wikipedia.org/wiki/Domain-specific_language#Domai...
[3] https://www.ultratechnology.com/1xforth.htm
[4] https://en.wikipedia.org/wiki/No_Silver_Bullet