Very nice landing page, but no screen shots? What does it look like? Do I have to install it and hope I make it through the wait list to find out?
Understand that you are excited, but the fact your website has next to no clear screenshots or descriptions of your value prop or system behavior is not confidence inspiring.
I think the lack of a dominant JavaScript domain model syntax has limited the availability of admin tools like django-admin. Maybe something driven by OpenAPI/Swagger model definitions?
It is ancient and no longer upgraded (and based on angularjs), but I'd argue that ng-admin (https://github.com/marmelab/ng-admin) is the fastest SPA/JavaScript admin framework out there. It is a bit opinionated about paging and filtering (and painful to do moderately complex UI customization), but beyond that I have seen nothing that has come close to the same level of "quickly get CRUD admin UI available" in react/vue land, largely because (similar to django) it had its own domain entity model.
The same team moved from there to react-admin, and looking at a couple of react-admin experiences I've been involved in I'd argue that it wasn't aiming for the same ease of use.
One question I have about this approach: if I temporarily include a security token in one of my files, will that get included in the temporary commits? And if so, how can I make sure that particular piece of history never makes it off my dev machine?
One possible suggestion is a one-time payment option. In a couple of my projects I have daily/weekly/monthly plans that allow people to pay up, use the features and then go away without worrying about long-term financial consequences. Maybe an option were someone can pay up, export their data and then whenever they want to import it back in they sign up for another short plan.
It is a DSL for additional logic that can be:
- Stored in your existing data store (assuming your data store can store a string)
- Executed without eval() or any other potentially dangerous method
- Executed in bounded time
You think of things like Lua in Redis: this is one take on a not-quite-as-capable alternative for logic that can be safely executed in restricted environments (barring errors in the implementation of the parser).
There will be editing/verification requirements: writing any moderately complex logic structure without a designer/test evaluator would be a nightmare, but as a generic way to specify/embed custom logic in a system that is language independent, has effectively no additional parser requirements (given that just about every single language has a JSON parser that is probably already in use in your project) it isn't a completely bad look. S-expression parsers do exist, but I'd wager many more people are familiar with the JSON parser in their language than the S-expression parser available in their language.
I will say: it isn't complete. It lacks clarity about the behavior in the face of missing/invalid operation arguments. Something like
{"<" : ["ham", 42]}
I'd assume would throw an evaluation exception of some kind, but that should be clear in the spec.
The playground at https://jsonlogic.com/play.html is a start, but before you try handing this to a non-developer, you'd really want a visual editor with node folding of some kind (so you can hide deeply nested structures away while you work on other things), variable completion (so you specify a sample data object and if you're typing in a variable you get completion options) and operator parameter verification (to stop you from writing in incorrect/unsupported values based on the operator).
I really like it! Have you given any thought to server-side execution? One of the things I think is missing from Jupyter is a clean, standard way of doing timed execution of a notebook: there are a number of paid solutions, but nothing out of the box (that I could find; spent a few days searching). Conceivably one could string together puppeteer or something similar, but it would be great to be able to run "node starboard_runner.js <notebook file>" and have the results output to stdout or saved to a file.
There's a personal taste element: I agree with you that certain WaveNet voices sound better (I've actually used them for video narration with some success). The breathing caught me off guard: it took me a minute to identify THAT as the element that was there but I implicitly wasn't expecting to hear.
The breathing + pausing at commas/full stops and general cadence was frankly superior to what I've seen with Google Cloud Voice, which is why I was curious if preprocessing was done. I've generally had to do multiple manual passes with Google Cloud Voice to get audio output that didn't sound robotic.
As an aside: I've been reading the AWS blog posts from Jeff Barr, but ignoring the Amazon Polly audio conversions. I actually listened to it today, and not only is it not terrible, but there's a moment (around 1:05 in or so) where you can actually hear an inhalation! I know @jeffbarr is sometimes in these threads: is that a standard feature of AWS Polly, or is there some preprocessing that is generating SSML to control cadence, and if so how do we get our hands on THAT?
The article talks about "constitutional rights": hence the US constitution link. You may not be in the US: in which case, you're right, you shouldn't care.
The usual counter example to statements of the form "You are not free to do something if you are threatened with jail-time or murder or getting beaten or ... ." is "if you yell fire in a crowded theater, expect to get in trouble". You're free to yell, but there WILL be consequences.
You can say whatever you want: you should also expect to take heat from non-like minded people. At some point the free speech concept transitioned to "I should be able to say whatever I want with no consequences". The First Amendment is very specific:
"Congress shall make no law respecting an establishment of religion, or prohibiting the free exercise thereof; or abridging the freedom of speech, or of the press; or the right of the people peaceably to assemble, and to petition the Government for a redress of grievances."
Says nothing about any one else's responses to your words.
I'll echo this: 30% is terrible, till you consider the alternatives. Before the app store it was 3 month lead times via a broker to hopefully get in front of a carrier rep who would usually go "meh" and send you packing. If they liked it, they'd take (if you were lucky) 50% with holds of up to 3 months on payouts.
Can't say I'm a huge fan of the 30% haircut, but I get to push my product directly to millions of people in a week and get paid monthly? What a time to be alive.
I can answer this one. Sometimes you have lines like this:
FROM ubuntu:focal
RUN apt-get -y install libssl-dev
<your app details>
Since libssl-dev gets periodically updated (security updates and whatnot) if you build this now and build it again in 1 year you're very probably not going to get the same OpenSSL version. So it MIGHT be reproducible, but can easily give you different results depending on updates to the packages and the way your Dockerfile imports external dependencies. And that's before we even mention updates to the base container image.
Of course, you can refer to a specific container image id and pin all your packages, which would go a long way to improving reproducibility.
Very nice. In a similar vein, I've used https://ricostacruz.com/flatdoc/ before, which is a bit more full featured and includes support for code samples.
Quite promising: one thing that would probably accelerate adoption would be to provide at least one language parser that can go to/from the format to a data structure of some kind.
Understand that you are excited, but the fact your website has next to no clear screenshots or descriptions of your value prop or system behavior is not confidence inspiring.