My mental model is as follows:

- Palette: All primitive color values.

- Luminance mode: light and dark modes (what CSS and operating systems call "color scheme").

- Contrast mode: Default and high-contrast modes.

- Color Theme: The named aesthetic identity like "espresso", "summer"... expressed as palette values mapped to semantic roles (surface, primary, text…), defined for each luminance × contrast combination.

For example, a website might have:

- 3 color themes: "monochrome", "espresso", "summer".

- Each color theme might support luminance modes, like "espresso-light" and "espresso-dark".

- Each luminance mode might support contrast modes as well, "espresso-dark-default" and "espresso-dark-high-contrast".

- Palette is all the values that "espresso" color theme consists of including luminance and contrast mode values.

The combinatorial complexity might look scary but most products only need a slice of it: two luminance modes, no contrast modes, one color theme.

Take this example: when a checkout button on an ecommerce website/application is triggered, the button should reflect that state and prevent re-triggering the same action so the button has to be disabled, then ideally a loading state has to be shown. When that action fails, an error may need to be displayed. Ideally you would use native DOM states first, ARIA states may be used if no native DOM states can be used, and if that's not enough then custom data states may be necessary.

Styling should be reacting to application state, preventing impossible states and bugs to create predictable UIs. Thus, styling is also a state management concern. UI=fn(state).

Comments URL: https://news.ycombinator.com/item?id=46753508

Points: 5

# Comments: 0

From their Usage Policy: https://www.anthropic.com/legal/aup "Circumvent a ban through the use of a different account, such as the creation of a new account, use of an existing account, or providing access to a person or entity that was previously banned"

If an organisation is large enough and have the means, they MIGHT get help but if the organisation is small, and especially if the organisation is owned by the person whose personal account suspended... then there is no way to get it fixed, if this is how they approach.

I understand that if someone has malicious intentions/actions while using their service they have every right to enforce this rule but what if it was an unfair suspension which the user/employee didn't actually violate any policies, what is the course of action then? What if the employer's own service/product relies on Anthropic API?

Anthropic has to step up. Talking publicly about the risks of AI is nice and all, but as an organisation they should follow what they preach. Their service is "human-like" until it's not, then you are left alone and out.

Banned and appeal declined without any real explanation to what happened, other than saying "violation of ToS" which can be basically anything, except there was really nothing to trigger that, other than using their most of the free credits they gave to test CC Web in less than a week. (No third party tools or VPN or anything really) There were many people had similar issues at the same time, reported on Reddit, so it wasn't an isolated case.

Companies and their brand teams work hard to create trust, then an automated false-positive can break that trust in a second.

As their ads say: "Keep thinking. There has never been a better time to have a problem."

I've been thinking since then, what was the problem. But I guess I will "Keep thinking".

If you use Google products extensively and don't use Apple ecosystem integration features, then Chrome may look like it has better features; the same is true if you are on the Apple ecosystem (Notes, Reminders, Calendar, Passwords, multiple devices, etc). Seamless integration of Apple devices is one of the biggest advantages of using Apple software like Safari, where you can use iCloud Tabs to switch between devices. Also, Tab Groups is a neat feature; you can move Safari windows to an iPad with Sidecar and so on.

Google's ecosystem also has similar features, but you can argue that you're "locked into a walled garden pretty tight" with Google as well.

Browsers have their different advantages, but they are not so different from each other, especially when we compare Safari and Chrome. Maybe the only real difference is that Chrome has way more extensions.

Comments URL: https://news.ycombinator.com/item?id=44385199

Points: 2

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=44150286

Points: 7

# Comments: 0

For me, biggest issue with CSS is how it's taught, how it's learned and mental models around the concepts. Most people have a different mental model of how the underlying system works, and this mismatch results in developer trying hard to bend CSS to his will.

CSS may be good or bad, there can be a better alternative... but are there any practical change that may happen soon enough that we stop learning and understanding how CSS works? Even we have a new language, people will try to use it as they used CSS before, so those intelligent people may do the same mistakes again.

We are stuck with CSS, whether we like it or not. I've been writing CSS since 2001 and it progressed immensely, still there are many things that's not possible to do easily with only CSS. But still it's the only thing we have for now and to make it better or to make a better alternative we have to understand how it works before just saying "i need a new tool", as the new tool may have the same issues as well.

I guess to change these 3 property on the same condition, you need to write this TW classes (or create a "variant" in separate config file): class="dark:contrast-more:focus-visible:enabled:data[intent=destructive]:border-slate-700 dark:contrast-more:focus-visible:enabled:data[intent=destructive]:bg-slate-50 dark:contrast-more:focus-visible:enabled:data[intent=destructive]:text-gray-50"

Or am I missing something that Tailwind makes it as easy as writing these states and combinations in regular CSS (without apply, which TW creators don't recommend using)? If that example is the preferred way of writing TW, and it's only 1 condition combination, I would happily switch back-and-forth files and write regular CSS without that syntactic high-fructose corn syrup.

What people misses out is CSS should be written in state-based architecture. For example for a button you have idle, hover, active, focus, focus visible, disabled states, and combinations of each button intent (default, primary, destructive, confirmation, warning) and color scheme (dark, light, high-contrast, low-contrast) states. Each of these states should enable-disable or modify some prop of the element, in most cases combination of different elements (sibling, child-parent). Trying to write them in inline classes is a PITA, especially the main concern for choosing that direction is just so we don't have a separate CSS file or need to find a name for the class (if you have a component, which Tailwind creators recommend you should, then you already need to find names for your components).

Also in addition to having separate component, component test and view/layout components; we also have separate hook files, separate state/context/store files. Even the component files doesn't encapsulate its own logic inside the same file anymore as to increase reuse of such logic. Somehow we practice separating almost every thing in the frontend to its own file, but when it comes to CSS it's too much "back-and-forth".

Instead of learning/memorising CSS properties and values, you learn and memorise Tailwind classes which are just abstractions to regular CSS properties and values and you need to write them inside class tags. I think the lure of Tailwind comes from IDE integrations and its documentation. But it doesn't add any "new features" that enables rich web applications which CSS lacks in anyways.

Dance Music Manual (http://www.dancemusicproduction.com) from Rick Snoman, version 4 has been recently released and it's the only book you need (for a time being). I don't own it but Secrets of Dance Music Production looks good too.

Melodics (http://www.melodics.com) is also good for practicing keyboard, if you're interested in learning to play the keyboard.

Music Production is very similar to front-end development, especially Javascript development. Your hardware-software studio is like your bundle system, continuous integration etc. So there are many moving parts to learn and it takes time and many many readings (books, blogs, forums, facebook groups, music store product descriptions etc.). It also takes time to develop your ear and in time you will see that new levels will be opened in your mind, like a game. You will hear more details, you will easily describe the qualities of the sound (is it sine wave or a square, what kind of sonic movements happening, what kind of effects with what kind of settings make that specific sound sound like that)

It's fun, takes time, may take money (if you're interested in hardware studio and premium software plugins). But it's basically so much fun!

The problem Arabs faced after dissolution of Ottoman Empire is similar in a sense to Turkish people faced, in regards to the national awareness.

Ottoman Empire didn't dissolved because they chose the wrong side, instead it was huge empire consisting of many nation and spans over an enourmous area (East Europe, Anatolia, Syria-Iraq, Egypt, Arabia, North Africa), while the army and many government offices couldn't keep up with the developments of the time. Basically, Ottoman Empire dissolved because of the wrong politics and failure to renew itself. After the French Revolution, nationalism started to spread over whole Europe and this affected the Ottoman Empire most, not only consisting of different nations, but also different religions. Being a religious state (Islamic), main subjects were Muslims and non-Muslims, separated by Millet system according to religious affiliation. Government officials were either Turkish or Devshirmes (Christian boys converted to Islam and trained to be gov. officials), being Muslim even wasn't a qualification to be an official.

When nationalism sweeps Europe, Christian Balkan nations like Greeks, Serbians, Bulgars etc. started to rebel against the empire to found their own independent nation states, feeling comfortable as the empire was loosing power every day. In that situation, Ottoman government was trying to cope with "the problem" by supporting the empire-identity of Ottomanism, and only small number of educated people were following the idea of Turkish nationalism and to create a Turkish nation-state. This was all happening at the last decades of 1800s, and Ottomans lost Balkan region, latery Ottomans also lost Middle East, Egypt, Iraq, Arabia, North Africa. British Empire also supported Arab nations to rebel against Ottoman Empire, promising their own land (British Mandates).

Empire was already dissolved when most of the nations declared their independence. WW1 was just nail in the coffin, that officially surrendered Ottoman Empire and Istanbul to British Empire. After the end of WW2, Allied forces (British, Greek, French, Italian, Armenian) shared the remnants of the empire with Treaty of Sevres, but Ottoman Army generals and irregular Turkish armed forces rebelled against the invading forces and this resulted in the victory for the Turkish side in the War of Independence, and ultimately resulted in the foundation of the Turkish national state.

TL;DR: Empire didn't dissolved because of choosing the German side. And also Arab nations didn't share "ottoman" ideals as Turkish and even many non-Muslim millet did and finally rebelled against Ottomans with the British support. Saying Ottoman Empire was an Arab Empire is simply ignoring the historical facts. This is not so different than saying all the Christian nations in Europe are descending of the Jews because Jesus was one. Having words from a language and having the same religious affiliation doesn't make two different states, nations or cultures one.

https://en.wikipedia.org/wiki/Decline_and_modernization_of_t... https://en.wikipedia.org/wiki/Rise_of_nationalism_in_the_Ott... https://en.wikipedia.org/wiki/Turkish_War_of_Independence

Comments URL: https://news.ycombinator.com/item?id=20095443

Points: 1

# Comments: 0

I want my city to be better and i want workers to do this. -Immigrants? Not in my backyard.

I want my city to be culturally rich and i want to be proud of the art that created in my city. -Punks? Unemployed artists? Not in my backyard.

Because of this, these people located in Kreuzberg... many many years ago, before the Wall even came down.

Now the wall came down and the same people say:

I want to have a nice and cheap(er than my area) office next to Landwehrkanal in Kreuzberg. -Immigrants and artists next to my office? Not in my backyard.

You repeatedly write that this happens because of some snowflakes' NIMBYism. Which is definitely not.

If we were talking about any other city in the world, whatever you're saying would make sense... because from the outside it looks like "oh the people who moved to city center doesn't want anybody else to move there".

That's not the case with Berlin.

Maybe you missed the topic recently but there was WWII and then East Germany, with Berlin Wall, death strip in between and East German State Police Stasi... and people who wants to escape from East.

Of course all of these happened in the city center, because the wall separated the city from the middle of it, and the areas once city center, become the dangerous ghettos.

The canals in Kreuzberg has become grave for some immigrant (and German alike) children, because it belonged to the East. If any child accidentally falls in the waters and scream for help nobody could save them. Because anyone who would enter the canals would be shot by East German police. And they did. And people couldn't save their kids from the waters, after these incidents happened. This is just one of the disadvantages of living next to a death strip, in the epicentre of the nuclear cold war.

Because of these dangerous properties, the place was cheap. And people in more "hip" areas didn't wanted to rent their flats to young people, artists, punks etc. So these people find home in Kreuzberg.

But yeah, feel free to forget about these context and try to blindly invalidate peoples experiences.

---

I gave the same example in another comment: There are many shops in Kreuzberg, which are located there for let's say 50-60 years. There are grocery stores, bakeries, markets, shoe repair shops, cheap quality restaurants, local bookstores etc.

But these people has to go now, because there is better buyer, who can afford the prices that these people can not. Or they have to increase their prices too. You were buying a croissant for 0,40€... now it's 4€. But hey, you can like our instagram page!

Now you're accusing these people of b+ching about the development, and you think they're greedy and they get what they wanted, now they're protesting so others can not get what they have?

Or do they want to live in the area, where they've been living for the last 60 years, and experienced many many disadvantages of the area?

The area was ghetto, so unwanted people located there. Now the area is hip again (after 100 years), and the people who lives there is unwanted again.