cstone
Joined 17 years ago
Joined 17 years ago
By my reading of the map, it means that that Midway Rising will cover the Salvation Army store and everything west of it between Sports Arena and Kurtz St (including the current parking lots).
Of course, if/when Midway Rising does happen, it'll probably spark future developments..
I saw it in practice a few times this year during spring training games, and it was _fast_. Add to that the fact that only pitchers, catchers, and hitters can request one (no managers holding the game up while the replay room checks on it), and it really won't slow the game down at all.
The best approach we've found to tracking specific app use time is to have our app publish App Intents, and then tell users to trigger those intents with shortcuts. It's fairly effective, but very clunky to set up and has to be done app by app..
We have a REST API with python client lib (https://fulcradynamics.github.io/developer-docs/), an MCP server (https://fulcradynamics.github.io/developer-docs/mcp-server/), and did some experiments with ChatGPT actions as well (https://www.fulcradynamics.com/chatgpt).
It doesn't have the simplicity of a plain export to duckdb/sqlite, but it definitely helps solve a lot of the sharing/collaboration problems.
Open-source VAX OSes weren't so lucky. BSD's libm used EMOD pretty heavily (for modf() and the like), and this caused problems in unexpected places if you happened to be running on a newer machine that didn't have these instructions (stuff like: awk would crash!). So the OSes had to follow suit as well, at least for the instructions that libraries / compilers would emit (which fortunately excluded most uses of the G and H floating types). The documentation available at the time was okay but.. imprecise.
source: I wrote the EMOD implementation for OpenBSD/vax a long time ago; POLY had already been done by NetBSD. It's still there! http://cvsweb.openbsd.org/cgi-bin/cvsweb/~checkout~/src/sys/...
uhh, right. two articles from the 90s put it in mclean, va: http://www.recordnet.com/apps/pbcs.dll/article?AID=/19940101...
We live in a world where device vendors (even small ones) routinely use technical means to thwart hackers and other tinkerers. Often, this is done under the guise of usability or security (sometimes with some justification, even). Plenty of people don't mind trading away some control for stability or ease-of-use.
This is a forum for hackers, and you just called your device "hackable". I'm saying that it's not, currently; it's a black box with an SDK that does cloud compilation. You don't document that fact anywhere or provide an ready alternative, and there's no information about what's underneath your API, either OS or hardware.
From the terms: "hereby grant to Allerta a perpetual, irrevocable, non-exclusive, worldwide, royalty-free license, with the right to sublicense, to reproduce, distribute, transmit, publicly perform, publicly display, digitally perform, modify, create derivative works of, and otherwise use and commercially exploit any text, photographs or other data and information you submit to the Website (collectively, User Generated Content) in any media now existing or hereafter developed, including without limitation on websites, in audio format, and in any print media format."
Getting people up and writing code on devices quickly is awesome; but sending code (unencrypted, even) off is pretty shady, particularly since you're not disclosing it to anyone.
Arduino manages to have a cute little barebones IDE based around an actual compiler; and they provide full hardware docs, links to datasheets, the works. You're doing exactly the opposite of that. Even Apple will let me compile code for my own iOS devices -- after I've paid the $99/year fee or jailbroken, of course...
The SDK's compilation tool doesn't invoke a compiler; it uploads your code to a service running off of http://174.129.29.50:8080.
The Arduino is fantastic because the bootloader is open-source, the hardware is open-source, and it's easy to find out full information about the hardware and pull the MCU datasheets yourself.
the downside is that it's not wireless, so you need a separate device speaking USB either way..
cofounder @ <https://fulcradynamics.com> / prev: veracode, guardent
socal