366 karma · joined August 8, 2012
i have a backend tech stack that i believe is scalable and efficient (REST or websockets). i'd like to prove this out with a demo or app. i can do a pure-js SPA frontend (eg fitno.us) but i'm terrible at UI so it's not gonna be pretty
is there a free service that i could provide that people would use at high scale ? there doesn't need to be a way to eventually monetize it
required: store data to database optional: rest calls to 3rd parties
anyone have an idea they're willing to share ?
whether that was a pittance or significant would depend on the price you chose and the popularity of the project
thank you (and the other commenters as well) for taking the time to look at the license and have this conversation with me. it's now obvious to me that several things need to be clarified - people still may not like the license, but at least then they'd be not liking it for the right reasons
which class of users do you see as receiving exceptions ? one of my goals in writing it was to limit (via the assurances) the degree to which an owner could segment a market, eg it requires published prices, and if they provide low-cost licenses to one user, that user can resell them
and by the same token, the downstream is able to distribute directly (with or without source), and forward payment to the upstream, ie it's symmetric
if something like this license became widely used, it would make sense to adopt or build infrastructure to facilitate distribution of payments (perhaps licensezero ?)
are you opposed to using non-open-source software in general, or do you see the assurances that PUPL offers as too weak to be useful ?
i've more or less given up on the software that I intended the license for, but i mention license here in the hopes that one of these open-core companies will create, vet and popularize a license with similar assurances
for a user that chooses to go beyond the free terms, neither guarantees any limits on what terms the owner can dictate. my license was intended to address that uncertainty, eg max prices and right of resale.
thanks for taking a look - your comment sparked some thinking, to the effect that my terms might be useful as a fall-back for an AGPL (or Parity) base license which had never occurred to me before
i'm not familiar with any commercial licenses that are close, but i'm interested. do you have any links or suggestions ?
It requires paying for usage above a level, but is symmetric and permissive and makes future costs predictable, ie prevents the copyright owner from pulling the rug out from underneath you after you've adopted it. The software that I intended this license for never gained traction (so completely that no-one ever told me "i'd try it out if it was open source") so it's untested.
But if a popular software used this license, would you be willing to use it or contribute to it ?
I love the idea and it's been fun for me to make demos with, but I've gotten almost zero feedback on the API, and what I have gotten is "can you add a SQL frontend". And yet neither ORM nor SQL are loved
So the question (and I'm not suggesting that Db4j is the answer) is: "what's the API that would be most natural ?"
the federal govt as well (the irs has a 20 point checklist to help make the determination)
every contract i've ever gotten in the last 10 years has required that i indemnify the company against being classified as a worker, and then given instructions that violate that checklist, and been upset when i pushed back
started looking for a w2 on tuesday :(
https://galachoruses.org/sites/default/files/IRS-20-question...
for the rest, a lot depends on what your goal in doing the benchmarking is and what your target and testing machines are. if you're developing software to run in server environments under load then the rest don't make sense to me. 5 means you may be able to continue to use your machine for other light tasks and still get semi-reasonable numbers, so it's a maybe
one addition. if your tests are relatively short (and shorter is better in that it allows you to iterate quicker), they won't be run under thermal steady state. fixing the cpu freq, or setting a conservative max, will help
no need to prove that the regulation actually helps, no need to prove that the worker caused harm
we did do that, and they were, but for the most part, for the moment (at least) we've won - so it's no longer on the tip of our tongue
however, neither your link nor anything from a reputable site that i've found through google says anything about costs or current industrial production. do you have any data to back up your claim of low cost, or is that claim purely speculation on your part ?
unless there's data that i've missed, it doesn't sound like seawater extraction is currently economically viable
or that would somehow highlight that it's more complicated to get compliance from one that the other, eg because the required SQL is more complicated
so the taxpayer is on the line (at least, as much as they were in 2008)
while talking extensively about the nocebo effect, it ignores the fact that without media coverage a patient may experience side effects but not connect that effect with the switch from one drug to another, or may think they're imagining the effect, etc