News for hackers. Stuff that matters.

bassdigit

Re:Psion 5mx Emulator on Wednesday May 22, 2024 @02:07PM (#40444074)
The physical keyboard is king! For a long time I was looking for a modern alternative.

The 'GPD P2 Max' comes close and for me hits the sweet spot of offering a small size while not deviating too much from a comfortable typing experience, but it has a fan and I wish the battery lasted longer.

Re:Pluckable Strings on Wednesday May 22, 2024 @01:09PM (#40443394)
further idea: let strings resonate with the overtones of other strings being played

also: support different materials like steel/nylon/gut

Re:Tiny World Map on Monday April 22, 2024 @01:11PM (#40116395)
Re:Tiny World Map on Monday April 22, 2024 @04:02AM (#40112264)
I wonder if it could be even smaller when they wouldn't store all coordinates with 10 decimal places, at least for the label positions.
Hilarious that these outputs, depicting black founding fathers, popes, warriors, etc., overturn the narrative that history was full of white oppression.
Re:Adding type safety to object IDs in TypeScript on Wednesday January 31, 2024 @03:45AM (#39201511)
nice!
OP doesn't owe you an excuse for offering content for free through a technology you disapprove of.
Still not hard: In that case, instead of msg use sendMsg AND/OR in the second statement use { status, msg: resultMsg }, or just result and later result.msg.
Not hard: msg can be derived from the parameter name of the send() function and status is a fixed attribute of the result.
Re:Epicycle Clock by Sophie Houlden on Wednesday August 02, 2023 @05:13AM (#36968681)
Not quite, the "0" of the minute hand is always aligned with the direction of the hour hand, so it points >down< at 6:00 unlike an ordinary clock.
Re:Faceless Clock Makes Your Think Twice About How It Works on Friday November 18, 2022 @07:01PM (#33664834)
This year, Cartier took the idea to the next level with the "Masse Mystérieuse": An absolutely gorgeous watch with insane mechanics where the movement is the rotor.

[1] https://www.hodinkee.com/articles/the-watches-and-wondrously...

Re:Problems with AI-based monitoring startups (2018) on Tuesday January 26, 2021 @03:22AM (#25913642)
Look, three paragraphs beginning with "Look," give the article a rather condescending tone.
> Website design is poor. You could definitely do with a designer to make it look nicer.

Really, in what way? In my view it's clean and simple.

> You either need to make it cheap, like $200/yr, or much more expensive. Right now you are in no mans land.

Another unsubstantiated statement. How much market research have you done on PDF libraries?

Pricing is a sensitive topic and many factors play a role in it. Too many to be assessed by an armchair expert.

> Don't worry about it not being open source; that's fine.

Where did OP express any worries about it not being open source?

Re:Show HN: iOS Login Page on Wednesday April 01, 2020 @03:35PM (#22752730)
Birds sing seconds after ear-blasting gun shots. Really?
Re:The Top Idea in Your Mind (2010) on Monday March 23, 2020 @10:54AM (#22664650)
"So avoid disputes if you want to get real work done."

There is an exception: When a dispute forces you to view a topic from a different angle, like in rubber duck debugging.

https://en.wikipedia.org/wiki/Rubber_duck_debugging

Re:Show HN: iOS Login Page on Sunday March 22, 2020 @04:34PM (#22658378)
After thinking about it more, maybe I am wrong and there is a use case for these animations:

Small children like to look at moving things.

So it depends on the target audience. Toys or educational Apps are different from the business / financial context implied in your demo.

Re:Show HN: iOS Login Page on Sunday March 22, 2020 @02:57PM (#22657522)
Am I the only one who finds subtle animations much more pleasant?

I think there is a reason why it's dark when the stage set of a theatre is being changed between scenes, but with user interfaces somehow any rearrangement must be a distracting visual gimmick these days.

Edit: Seriously, why do you need a hard change to a blue background only to then move a white cloud up across nearly the complete height of the screen?

https://github.com/realpaliy/ios-login/raw/master/art/finalA...

Re:My favourite Git commit (2019) on Sunday March 08, 2020 @09:43PM (#22522177)
Not sure how to feel about being author of the most upvoted and also the least upvoted comment.
Re:My favourite Git commit (2019) on Sunday March 08, 2020 @08:45PM (#22521883)
The commit message succeeds in justifying the effort but lacks an in-depth understanding of the related mechanics. I can imagine the developer felt bad about 'only' committing a one character change at the end of the day and wrote the message to make up for it. Because of this un-economic outcome, he hesitated to dig deeper.

There is no reason to feel bad.

The cultural issue is bad management that still evaluates developers by lines of code / commit activity.

Re:My favourite Git commit (2019) on Sunday March 08, 2020 @07:07PM (#22521309)
I'm not a ruby developer but the actual problem seems to be the default file encoding.

There is a detailed blog post[1] about it, adding a lot more to understanding what's happening. More than a blog post about how a diary entry as a commit message made somebody feel.

[1]: http://graysoftinc.com/character-encodings/ruby-19s-three-de...

Re:My favourite Git commit (2019) on Sunday March 08, 2020 @06:55PM (#22521234)
No-break spaces aka &nbsp; can be quite useful for preventing line breaks for example between a value and its unit, or between label and value. Or when writing for example 'e.g.', although you could argue that in this case a NARROW non-breaking space U+202F would be preferable.
Re:My favourite Git commit (2019) on Sunday March 08, 2020 @06:45PM (#22521168)
Paraphrasing the first comment of the commit[1]:

A commit message with such a long explanation helps nobody, because it is not searchable by Google, not even by GitHub[2]. [...] If the commit message requires a blog post to be good (searchable) – it is a poor commit message.

[1]: https://github.com/alphagov/govuk-puppet/commit/63b36f93bf75...

[2]: https://github.com/search?q=invalid+byte+sequence+in+US-ASCI...

Re:My favourite Git commit (2019) on Sunday March 08, 2020 @05:23PM (#22520713)
It IS the no-break space. The hex UTF-8 representation of it is C2A0; you can find that sequence in original version of the file.
Re:My favourite Git commit (2019) on Sunday March 08, 2020 @05:17PM (#22520678)
It is U+00A0 [1], a non-breaking space [2], can be typed in some office applications using ⌃+⇧+␣.

[1]: http://fileformat.info/info/unicode/char/00a0/

[2]: https://en.wikipedia.org/wiki/Non-breaking_space

Re:My favourite Git commit (2019) on Sunday March 08, 2020 @04:53PM (#22520543)
Following this thought, it could be argued that the author did not even fix the problem, only eliminated a symptom of the underlying, serious configuration mistake that restricts file contents to an outdated character encoding.
Re:My favourite Git commit (2019) on Sunday March 08, 2020 @03:26PM (#22519961)
The author spent all the time documenting his journey but totally fails to explain the actual reason of the problem: If the file contains a UTF-8 byte sequence, why is there an attempt to parse it as US-ASCII? I get that it's just a wrong space, but if some day somebody actually want to put a UTF-8 char there for some reason, this commit essay wouldn't help at all whereas googling stackoverflow seems to deliver (unverified): https://stackoverflow.com/questions/15947425/rake-tasks-fail...