News for hackers. Stuff that matters.

rlevy

Re:Generative AI and ChatGPT Enterprise Risks [pdf] on Saturday June 03, 2023 @10:00PM (#36182337)
In the section on open source models, this is missing the important distinction of which ones have licenses prohibiting commercial use.
What’s the third book?
Re:LineByLine: Memorize Anything on Friday April 29, 2022 @12:42AM (#31201534)
That implies a good old fashioned one-time purchase
Re:Spring Core on JDK9 is vulnerable to remote code execution on Wednesday March 30, 2022 @10:19PM (#30863178)
Yes
I would good money to have something like this in a PowerPoint extension.
This is slick! Anything similar for languages beyond Python?
Re:Turing Tumble – Build Marble-Powered Computers on Wednesday September 05, 2018 @08:58PM (#17923170)
Agreed. I was surprised by how much my 6 year old became engaged in the story. He frequently asks to play/solve more so he can find out what happens next in the story.
This is neat but there’s a big gap between natural language search and conversation.
Re:RAML – RESTful API modeling language on Thursday September 10, 2015 @05:24PM (#10200653)
RAML is essentially a YAML with a specific schema. Tell your IDE to treat .raml files as .yaml and all the syntax highlighting, etc will work perfect
Re:RAML – RESTful API modeling language on Thursday September 10, 2015 @05:21PM (#10200638)
Swagger seems to have more awareness and adoption but we have fully embraced RAML due to its "composability" features which eliminate much of the boilerplate and copy/paste/tweak required by Swagger. Making the API spec easier to author & maintain is well worth the downsides of not being able to tap into the Swagger ecosystem. If we really needed something from the Swagger ecosystem, I don't think it would be difficult to create a RAML->Swagger converter. There is already a converter that goes the other direction.

But whichever one you choose, this stuff is awesome. We author API specs and then codegen mock services, client side wrappers (Angular services or Backbone models/collections), server side DTOs and controllers, and pretty documentation. Having that all done from a single authoritative text file under source control has drastically reduced the friction between frontend and backend developers.

Re:Pointer Events Now in Firefox Nightly on Wednesday August 05, 2015 @07:41AM (#10009041)
The pointer API is significantly easier to use for non-trivial interfaces so yeah it does make the world better. For now, yes you need to worry about all 3 API sets (or use a pointer polyfill that tries to do that for you). As older browsers phase out, you'll be able to switch to only working with pointer events. Same with any other new browser API - not super useful on day 1 but eventually there is enough adoption that we can rely on it.
1 rep in the house (who can't vote), no senators
Re:Tron-Club, a monthly circuit-building kit on Wednesday July 15, 2015 @07:02AM (#9890678)
Amazon and google are also words to find in a dictionary but that doesn't get in the way of enforcing their trademark
The trial at this point is entirely about copyright, not patents
Yes, on each side
Re:Excel-Based Automated Web Testing Framework on Friday June 26, 2015 @08:01AM (#9783724)
Authoring JSON in Excel does not sound like a productivity booster. That's painful and defeats the purpose of using Excel because of its familiarity.
That's not entirely correct - you also must write C code. You can write JS that runs on the phone and can do stuff like call web services, store data, and communicate with the watch. But it's old fashioned C code that you need to have running on the watch in order to render stuff, get sensor data, or exchange messages with the JS running on the phone.
the actual healthcare.gov (if you can get in) actually does a decent job of letting you compare plans in detail... there are far more factors to consider than just monthly deductible. various copays, out of network coverage, whether dental and vision are included, etc. this site does none of that