- Wouldn't 0402 be 4x larger (if comparing lengths) or 16x larger (if comparing areas), not 2.5x?
Edit: Nevermind, I was wrong. I see now that the sizes don't actually directly correspond to the number codes! 01005 is 0.4mm x 0.2mm and 0402 is 1mm x 0.5mm. That's annoyingly confusing, IMO.
- Yeah, I agree. The size and price are attractive and they are pretty capable, but the UI is a bit more complex than ideal. It either needs better labeling of functions/combos (which is hard to do with the size) or more buttons/knobs to reduce the number of combos. On that note, the cases do a bit to aid with the labeling, but they also increase the price by more than one might expect. With better UI, they could have been truly amazing.
- Do you mean plugging a 4k monitor in while gaming, or just in general? If just in general, something's going very wrong since I _only_ use my M1 (not m1 max, not m1 pro) macbook plugged into a 4k monitor (except when traveling), and it's never hot unless I'm playing a game that's really pushing the processor. For most games it barely even gets warm. And for normal web-browsing and netflix-watching it's cool to the touch.
- > During a fire in the Bronx, firemen laid 7,000ft of hose to get to a suitable water supply and the truck pumped as though it was dipping its feet into the ocean.
"7000 ft" sounds wrong to me. That's over a mile of hose. Feels like that's unnecessarily long. I'd love to learn more about this. Anyone know when or what fire this was?
- >> little help popup telling me places I can go. I really appreciate this because I don’t often use the “go to definition” or “go to reference” feature and I often forget the keyboard shortcut.
> Exactly! Pity this basic contextual help isn't more widespread, every single app that uses a lot of keybind sequences could benefit from it, especially if it becomes a bit smarter and only shows a popup if you don't finish the sequence right away
I agree 100%. This would be helpful in so many places. That was my favorite part of the article -- one little paragraph and screenshot, but it made me desperately crave that feature almost everywhere. I agree that it'd need to be smart about it -- after a timeout, as you mentioned, is a great idea. That way it can stay out of your way if you know what you're doing, and only pop up when you hesitate.
- I think kids aren't the best comparison with senior citizens when it comes to technology. I've got senior citizen parents and I've got nieces and nephews who are all under 10 years old. The kids are so much more adept at pretty much any technology they get their hands on when compared to my parents (iphones, nintendo switch, tv remotes, etc). They start off about as poorly as my parents do but quickly overcome them. My parents aren't tech illiterate, either -- my dad especially was quite a DOS power user back in the day, and to some degree has kept it up with his Windows usage too.
I think part of it might be due to the neural pathways still forming in the kids brains, but I also think a lot of it has to do with who they're around. The kids are around their parents who are using this tech all the time, while my parents don't have that benefit except for in comparatively small doses.
- You seem to be confusing the concept of a language with the concept of program used to write in a language. DEML is a language (that's what the "L" is for). A program with a UI, graphical or otherwise, can be used to create a DAG, and then that DAG can be saved in a DEML representation.
With that in mind, what you seem to be bothered by (please correct me if I'm wrong) is actually that a language has been released without a UI to abstract away the process of writing it?
- A learning experience (by making this game) is useful to the person making it. Honing one's skills (by making this game) is useful to the person making it. Taking breaks from work (by playing this game) is useful to those who need a break. Learning (by looking at how this was made) is useful to those who wish to learn.
Does it solve world hunger? No, not at all. But it is indeed still useful to some people.
- I don't think "it should be obvious". The world we live in is one where caber tossing, curling, boxing, cheese rolling, quidditch, and sepak takraw (to name just a few) are all sports. So "softball with a 16-inch diameter ball" really isn't so unbelievable of a concept that it should be obvious that it doesn't exist.
- I actually can't read things on that site at all. I move my mouse around while reading, not necessarily near the words I'm currently reading, so when my mouse disappears it's haltingly distracting. In addition to that, the way the "game" visually interferes with the text that I'm trying to read makes it incredibly hard to focus on reading. These two things combine to make this site literally unreadable for me.
I don't get why people keep posting and upvoting articles from this user-hostile site.
- This is pretty cool as-is, but I can't help but try to think up ways to increase the speed. (Not the point, I know.) I feel like it should be able to do a whole column pretty quickly with some optimizations. If the device that turns a block could do so without needing x-axis alignment to change, then you could do a whole column pretty quickly. Or perhaps it'd be better to do rows instead of columns, since the y-axis alignment shouldn't need to change with the current device. As for the block-turning device itself, I think some sort of thing that rotates would speed things up since you wouldn't need to reset, I think. I bet a manufacturing automation specialist could get this thing cruising...
BTW I love that you initially went with a very direct e-ink analog with the balls!
- We use Wordstock as our POS, our website is an IndieCommerce site (I'm quite adept at pushing IC to the limits), and we list on a couple marketplaces doing manual uploads of exports from our POS that were processed by scripts I've written.
The "brains of your bookstore" goal sounds great. If/when Bookhead becomes a full POS, then my store might consider switching, but until then, we've got 20+ years of history in Wordstock the product and with Wordstock the company, so Bookhead would need to be significantly better than our current system in order to be worth switching to. WS isn't perfect but we're used to it, and they've modified it in many ways as per our requests. And Jeff in their support department is the best customer support person I've ever dealt with anywhere for any reason.
- Interesting project! I'm in charge of all things technical at the book store I work at, so this piqued my interest. We've solved for ourselves many of the problems that Bookhead solves since we've been open for a few decades, so this doesn't seem like something we'd want to switch to, but I'm still bookmarking it and keeping my eye on it. Also I hope you don't mind me offering some suggestions/observations...
- If you're _not_ using AWS, I'd explicitly mention that somewhere. I know there are a lot of indie bookstores who care about avoiding Amazon and any Amazon services. If you _are_ using AWS, well, you might find that you get more business from indie booksellers by not using it.
- I'd add an explicit list of supported POS systems in the Overview of the docs. This was one of the very first things I wanted to check. (My store's POS isn't supported, btw.)
- I'd add an explicit list of supported channels in Overview of the docs, as well. This was also one of the very first things I wanted to check.
- I'd focus on adding Square as a supported POS. From what I see in the ABA forums, this kind of thing might appeal to the bookstores using Square as a POS. Especially if you can load the book data you have into their POS, possibly based on SKU? Maybe that actually would warrant a separate product you could offer (or that someone else could make).
- I can't believe I never knew about this! This could be useful to some of my workflows.
I just looked it up and here's an official help page about it: https://support.apple.com/en-tm/guide/mac-help/mchlp1341/mac
"Potential Delays: Because most postmarks are applied at processing facilities, the date inscribed may be later than the date the mail piece was first accepted by the USPS. This discrepancy is expected to become more common due to the implementation of the "Regional Transportation Optimization" (RTO) initiative and the adoption of "leg-based" service standards."