It's purpose is to never collide with another UUID v4, not to be the most unique value ever.
213 karma · joined December 15, 2014
It's purpose is to never collide with another UUID v4, not to be the most unique value ever.
UTF-8 is variable length anywhere, not just inside mysql. If you don't want this behavior, you can either use UCS-2 or UTF-32. UTF-16 and UTF-8 are variable length encodings, period.
Most databases that have use char length for unicode actually work with UCS-2, and use 2 bytes per char, like MS SQL Server.
I can confirm both these commands return 36 in my mysql installation:
SELECT LENGTH('15c915fc-4d50-11e7-9bc7-50b7c307c620' COLLATE utf8_general_ci);
SELECT LENGTH('15c915fc-4d50-11e7-9bc7-50b7c307c620' COLLATE utf8mb4_general_ci);
Now, if the developer don't know when it makes sense to use a UUID, there are certainly more problems in the application to worry about. Which is 99% of the cases in most business applications.
* uuid type
* datetime with timezone
* storing (and retrieving) the view definition as it was defined with comments, formatting, etc
* using the same temporary table multiple times in the same query
This is not an extensive list, but are things that bite me every day with mysql.
Even though it's not query cache related, I wonder why such basic features are still missing and what are the plans to include them? They sound much simpler and more important to add than adding a nosql protocol to a sql database.
A common fuel station here usually have 8 pumps, and usually 4 employees to operate at a time. Due to laws on working hours, etc, there may be 2 or 3 shifts. Without going into peak hours and different # of people per shifts, a standard station may easily have 10-15 employees. Then multiply what you pay to each employee by 2 due to taxes, etc.
Not saying it's the highest of the expenses, but employees in Brazil adds up to the operation costs. It's one of the main complaints in business here.
First, I wasn't implying investors are bad people. In fact, I tried to imply the opposite.
What I meant was that a lot of people (at least people I know) blame companies for making decisions that cut jobs, and investors for pushing in these directions.
But at the same time, nobody is so selfless in their own life decisions in order to sacrifice their careers for someone they don't know. In fact, most people will consciously decide to earn more and make their lives better even if that means other people will lose their jobs. For example, I doubt any software developer will ever change careers just because the software he works on will cause half of the sales team to be fired. That's what I mean by people not being so selfless in their own life decisions.
But when it comes to losing their own jobs, it's common to hear people say that companies or investors could decide take the loss, earn less and keep these jobs, like the decision was a choice between saving lives or killing puppies for 10 cents more, and someone is just too greedy.
So, by "expecting investors to grow this moral guideline", I didn't mean they don't have a moral guideline. I meant people expect a much higher moral guideline that would make them sacrifice themselves in favor of the greater good, while other people don't actually do it themselves.
Jobs must exist by market demand, artificially creating jobs is the worst thing a country can do. Every law had good intentions, it's always the indirect side effects that cause problems.
Having worked with MSSQL for years, MS hit the right spot with Management Studio. It's an UI focused on writing SQL, and any wizard has a "Generate SQL for this" button. It let me write huge SQL files, save them, reopen then and run them. When I found dbForge Studio for MySql, I felt at home. I wish postgres had something like that.
Last week I went through ALL the GUIs in the postgres wiki page and found nothing good. Valentina Studio and EMS are good, but not great. EMS has a lot of features, but honestly it bothers me it cannot even use the default system font in windows, the environment it's built to run on. It's like it's stuck in 2002.
If I could sum it up, the thing I miss the most is being able to work with SQL. I want the first button in the toolbar to be a "New SQL Query" that opens a huge editor that lets me write and run SQL. Not a "new database", not "new project". Amazingly, most postgresql UIs are simply terrible at writing and running sql.
It's like postgres uis are like the PHP of database UIs: people that like it have no idea how bad they are, and the very few people go elsewhere to see how much better the world is outside.
Your concept of good code design is close to what I mean, but even that is not possible in php.
> "PHP is a community of amateurs. Very few people designing it, working on it, or writing code in it seem to know what they’re doing. Those who do grow a clue tend to drift away to other platforms, reducing the average competence of the whole. This, right here, is the biggest problem with PHP: it is absolutely the blind leading the blind."
This is so true it hurts, and unfortunately if you think "it's not like that, every platform has goods and bads, php works for me, yadda yadda yadda" you're in the amateur group. You need to work with other platforms for real to understand this. It's not "every platform has issues", it's more like "every platform has issues, and then there is php, in a different category with much deeper problems".
This is not about preferences or tastes either. It's just about looking around and seeing how common problems have already been solved. PHP7 has good exceptions, yay! Except they should have been there for 20 years. It was already a very solid concept back when PHP 1.0 was released. ES3 implemented exceptions correctly in 99 for god's sake. Every other language did too, PHP is the only kid in the block that took 20 years to understand what exceptions are supposed to mean in the language.
I could point other small things like the new DateTime API being a joke, mysqli is still supported and still converts typed data to strings, terrible encoding support, pure byte strings instead of unicode strings, inconsistencies in implementations between OSs, the compiler still acting differently depending on php.ini settings, but in the end, it all boils down to bad design.
Facebook's Hack fixes the PHP language for real in strict mode, and that is the work of real engineers thinking about stuff. PHP7 is still the same old people trying to get around without looking at proven solutions anywhere else.
And that's why you can't design good code with PHP7. It's like trying to design a good house made of turd. Doesn't matter how much you design it, in the end it will still smell terrible.
PHP on the other hand remains shaped by people that don't understand how badly designed PHP is and how the decisions that drive its design process are different from almost any other language.
ES6 onwards may be far from perfect, but it's much more shaped by experience and good practices than PHP will ever be. This counts a lot, you can currently design good code with javascript, while even PHP 7 still makes it impossible.
The fact that wordpress websites are 30% of the web masks the fact that there aren't nearly as many php developers around.
Javascript won the web, PHP didn't. PHP is just another language with decreasing popularity according to the last TIOBE index: http://www.tiobe.com/index.php/content/paperinfo/tpci/index....
The only issue here is not realizing the email field in the git config doesn't need to be your personal one or even real. And I agree more people should know this, but this is not something github or git needs to fix in any way.
I'm not stating that these stats are the ultimate sources of truth. But those are good references. If you were to measure the reality in most countries, I doubt those numbers would swap places.
In Brazil I see lots of devs using Macs too. It's just not the majority of them.
Note that I'm not from the US, I'm from Brazil. Here windows pretty much dominates the landscape.
But this is also important: while the US is currently quite apple-centric, most countries are not. And although the US concentrates a lot of tech companies, it's still only 4% of the world.
What I mostly miss is a good tool focused on writing SQL like Management Studio from MS SQL Server. Something that allows me to easily open complex large scripts in a full editor, execute parts or all of it easily and get results back. Not much gui, not many wizards, but a good experience. Most tools I find for pg are either full console or full guis with too much focus on wizards. It's like the people using it are uncomfortable with SQL for some reason.
But having followed pg for 15 years or so, I don't think they want or need to be the most popular database. They just want to be a damn good database server, and they are.
You won't get comments, but you can read the code very clearly.
As I get older (I'm still 33), I realize more and more that almost nobody got their stuff together. Most people even in their 40 or 50 are still trying to figure out what to do with their lifes. They change careers, move to a different state, start writing books, start some business different from what they have done their entire life.
When I was young, I always heard that 'life is hard'. I live in a third world country, grew from a poor family and never had much money. But it wasn't until I was married working in a good company that I realized what that means.
I realized that life being hard is not about not having money or a family... these are struggles we all have. Life being hard is all about these choices you have to keep making that are not confortable at all, you can never rest, life is always changing your plans. Even when you think you have it all figured out, this will last only a few years and you will have to start again.
It's all part of life. We all have struggles and the sooner we realize that it's all about the journey and not about the ends, the easier it gets to go on.
You have exactly the same issue with setTimeout. Errors will be thrown when the function runs, not when you schedule it. The problem you're describing is not an issue, and that's why today there are linters and compilers.