My experience at the time was that it was perceived as not serious enough and lacking important features. If my memory isn't very bad, I believe as late as 2000 SQL Server still only supported AFTER triggers.
In my experience in the late 90s and early 00s, besides Oracle and Sybase, DB/2 and Informix were also regarded as good. Oracle was considered the best though.
Thanks for the clarification, I guess my memory is very bad after all! :)
Do you remember if that was a recent addition?
Full disclosure: I was quite the newbie back then and most of what I "new" about SQL Server was what the more experienced coworkers told me. This was a very IBM-biased place so I'm not surprised they would have stuck to some old shortcoming, like people who still talk about bad MySQL defaults that have been changed for at least 10 years.
Up until that job (which was my second Actual Formal Job), all my DB experience had been with either dBase (I think III plus or IV) and access, so this was a whole new world with me.
It was through MS SQL Server that a colleague taught me about backups and recovery, after I ran an update in prod but forgot to include the where clause ... :)
You can still rip CDs with Apple Music. In fact, that's the only use I have for that app (I recently lost a hard drive with music and I'm in the process of backing up all my CDs again).
I took it as a napkin rounding of 365/7 because that’s the floor you pay an employee regardless of vacation time (in places like my country you’d add an extra month plus the prorated amount based on how many vacation days the employee has), so, not that people work 50 weeks per year, it’s just a reasonable approximation of what the cost the hiring company.
When traveling abroad, it always surprises me when I’m asked for my id when buying alcohol. That’s only a thing in my country when you’re in the age bracket in which it’s risky to tell your age just by your looks, but after that, I haven’t been asked for my id since at least I’m 20 or 21 (drinking age is 18 here).
Prescription drugs are different because those are tied to your name anyway, and that’s why medical information has a different protection standard.
As a parent of 2 I think it’s better to talk to your kids, check what they’re up to, and, you know, be involved in their lives. Also, as a former kid, if there’s something they want to do but you don’t want them to: they’ll do it. Better that they know they can trust you to say “I still want to do X” than have to do it in hiding and without your support if anything goes wrong.
I agree about the duct tape, which I also use often around the house, so maybe that's why I like org-babel :)
Just wanted to say that I share data between different blocks in different languages through files and env variables (I add :session shared to the src blocks that need to access this). That is useful also to have src blocks you can execute repeatedly and that depend on something like an aws identity being assumed (you just assume it in the first block that shares the session).
I agree it's messy, it's just a mess that works for me.
I think this is the crux of the issue, use like this is like a real program, just built up incrementally in a notebook rather than a repl or shell-with-pipes, and with manual error handling. The STEPS project was all about this- a way of incrementally building blocks that can be composed.
With org mode in mind, ideally you would have language support for this ie. Comments are scoped metadata that can be formatted, tested, linked etc.
You need a well defined spec like djot as a DSL for this to work, so that parsers can be easily written for it. This level of language support allows many different views onto the source code. We’re not there yet.
I use org a lot, in fact, it's my daily driver. I also have to deal with MySQL, and, if using the vertical output (what you get if you finish a query with '\G' instead of ';' it makes pasting into an org file a pain.
Sure, not a big pain, I just wrapped it in a function paste-from-mysql that appends the whitespace, but then I need to take out the whitespace of I want to paste that somewhere else. It would be nice to have org support some sort of 'do not interpret what comes next' block markers. I guess someone with enough time and skills could make this change but, alas, that's not me.
Thanks! I had actually seen that, but didn't realize that org does remove the leading comma when you extract a block to paste it somewhere else, which is great, because it means I need one less function.
Now I just need to keep my paste function, but have it add a leading comma instead of a space, and I need to use example instead of src (not a problem for this use case since, even though I normally paste them into sql src blocks, the syntax highlighting isn't that useful.
You gave me a nice little task for a rainy day, thanks :)
What if you're building a product for other people like you to use?
I think this is very common, like people building tools for trackers vs Ableton/Live/etc style DAWs, or those writing software only targeting the OS they use? Not every product is built with the goal of worldwide adoption.
Back to the specific case being discussed, I can easily export usable markdown from org. The people I share it with have never noticed it wasn't markdown since the start, so why wouldn't I continue to use org even when interacting with people who don't? It makes my private side of the exchange better for me, and it doesn't affect the public side negatively for others.
Yes, though in the case of driving, if I prefer driving on the left, I'd have to move, since I live in a country where you must drive on the right, but to use org-mode instead of markdown, I just ... use org-mode?
I'm afraid I don't understand your point here, sorry.
In my experience in the late 90s and early 00s, besides Oracle and Sybase, DB/2 and Informix were also regarded as good. Oracle was considered the best though.
reply