|
Yeah, it is hard to understand why one should ruin such a good cheese...
"The only place where Success comes before Work is in the dictionary." Vidal Sassoon, 1928 - 2012
|
|
|
|
|
OriginalGriff wrote: Why? Just why, Scandinavia?
Until I saw this, my impression was that they were such polite, civilised people. It just shows that even the best of us are only one step away from barbarism. 
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
Could have been worse, imagine they had used Gouda instead 
|
|
|
|
|
I drink mine with hot chocolate.
Cheese that is! 
|
|
|
|
|
Strangely enough, I haven't seen that flavour combination on Masterchef, but ... it's not as bad as cheese in coffee!
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
I think a chocolate coffee is common enough.
We have the Wiener melange, which is choco coffee, but which is not how they drink it in Vienna 
We also have the choco coffee, which has less choco than the Wiener melange, I think.
I found both to have too few chocolate so I now take an espresso and add a cup of hot chocolate to it.
It all comes from our coffee vending machine at the office.
Basically, I don't drink coffee, but I sure as hell need my shot sometimes.
By sweetening it with chocolate (which has lots of sugar from those machines) it becomes bearable.
|
|
|
|
|
Never heard about it until now.
But after having checked it out it seems to be something people in Tornedalen are doing.
Tornedalen is a valley on the northern border between Sweden and Finland, and about as representative for scandinavia as the Orkney islands are for the Irish.
Wrong is evil and must be defeated. - Jeff Ello
Never stop dreaming - Freddie Kruger
|
|
|
|
|
I think you need to include more than just Tornedalen. I think most of the samis use or at least used to have "kaffeost" in their coffee. They also used to put salt in the coffee.
My mother used to make "kaffekött", translates to coffeemeat, which basically was ribs of a "cow" in the oven for some time, I don't have the recipe and she's gone to a place where she can't answer any questions, so I don't know how long. Since I don't drink coffee I don't know exactly how it would alter the taste of coffee. It was fairly salty so I imagine it wold be a bit like salt in the coffee.
modified 23-Nov-20 8:14am.
|
|
|
|
|
Totally out of my sphere of knowledge.
You're probably right.
Wrong is evil and must be defeated. - Jeff Ello
Never stop dreaming - Freddie Kruger
|
|
|
|
|
I have argued this with lots of USAnians who insist that in English (or rahter: American) language, "Scandinavia" includes Finland. No matter what the Scandinavians themselves say.
Obviously, any language is free to redefine whichever term it wants to, but it is rather uncommon to do so with names. If Scandinavians claimed that "In our languages, USA does not extend to the west of the Missisippi", we are in principle free to do so, but I guess lots of USAians would have strong objections to the definition.
Scandinavia is Denmark, Norway and Sweden. The Nordic countries is a larger group, including Finland, Iceland and the Faroe Islands.
I have never seen cheese made from reindeer milk in any grocery store in Scandinavia. I have never been offered it, never tasted it. Reindeer is herded by the Sami indigenous people. Traditionally, the Norwegian and Sami population has had very distinct cultures (today, the borderlines are blurred, though), the Sami, as well as the Finns, coming up form Hungary a few thousand years ago. The Finish and Sami languages split apart about 2000 years ago, but belong to the same language group as Hungarian - very distant from the Scandinavian languages.
The Sami certainly has a number of food traditions that Scandinavians find rather peculiar. If a Sami told me about this reindeer cheese soaked in coffee, I would certainly trust it to be a Sami tradition. But it is certainly not Scandinavian style.
(We do make cheese from sheep and goat milk, though, but that is something different. Also, if you have been served the brown "goat cheese", commonly used on waffels, it is strictly speaking not a cheese, but what is left as whey, a byproduct when you remove the cheese from the milk, and then boiled to evaporate most of the water.)
|
|
|
|
|
I think that's the only way to make a Starbucks <anything> taste decent.
|
|
|
|
|
I had an Excel sheet I wanted in my app - so I converted it to CSV (which Excel will output), then rethought - do I really want to play with CSV data, when the rest of my app is JSON and includes Newtonsoft already?
Nope. So one quick online converter later (CSV To JSON Converter[^] - free and works!) and I've got it in JSON.
Then it was the "sod it!" moment: I'd really rather have that in a DataTable ...
Bingo! 11 characters added to the file later, and it deserializes as a DataTable!
It's just sooooo friendly! 
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Me too. Html table serialized to a json string. sent over the controller, converted to a dynamic list then off to the sql database. While it's easy when you know how, ultimately there is little heavy lifting for the "coder" to do.
|
|
|
|
|
Html table --> DataReader --> SQL Server via BulkCopy
Profit.
|
|
|
|
|
You're working too hard. 
One of the utilities I've been working on at work recently is a very simple ETL tool.
Source Destination
CSV Y Y
JSON F F
Sharepoint (list) Y N
SPLUNK F N
SQL Server Y Y
SSAS (OLAP) Y N
XHTML Y Y
XLSX Y N
XML Y Y
Y=Yes , N=No , F=Future support possible
Each "source" provides a DataReader and each "destination" reads a DataReader.
One design decision I made was not to use any third-party technology (e.g. Newtonsoft), it's all .net -- it doesn't use interop either.
I intend to add reading and writing JSON to it once I have .net 4.7 or newer -- which supports JSON natively.
The point being that opening an XLSX file and wrapping a "worksheet" in a DataReader is not all that difficult -- non-trivial, yes.
With the DataReader, you can create and populate a DataTable, but what do you do with it then?
|
|
|
|
|
Great stuff
I'm just working on a similar thing where you can also inject a database scheme and with this it does recursively collect the data from any starting record from a table. Additionally this part does also support the mapping of 'internal technical id' (usually an integer in my case) against 'user id' (usually a nvarchar(n) in my case).
Nice challenge to solve it in general for compound keys of any data type, detect self references on the same record, detect circular references...
Quote: With the DataReader, you can create and populate a DataTable, but what do you do with it then?
o Briefcase to exchange data (e.g. customer has a specific problem and you need to debug)
o Importing data from e.g. Excel (often ask by customers)
o ...
It does not solve my Problem, but it answers my question
Chemists have exactly one rule: there are only exceptions
modified 19-Jan-21 21:04pm.
|
|
|
|
|
Definitely my favourite format for passing around information too.
It makes me wonder who would want to use XML, or rather why on earth XML became so popular when JSON simply lets you pass objects around between different platforms/services.
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
|
|
|
|
|
Because XML is more robust, it allows finer granularity than JSON, the ability to apply attributes to values is vital in many cases.
SQL Server has an XML datatype and functions for working with it.
When I read a JSON file, I convert it to XML so I can store it in SQL Server and query it.
JSON is fine for simple data transfer, as it is intended, certainly better than CSV.
Use the right tool for the right job.
|
|
|
|
|
Sure, one of the advantages of xml is that you can check that it is correctly formed before importing it while JSON is much more "free".
Interestingly enough I had to do some work recently deserialising some XML and the advantage was that it was fairly straightforward given the libraries available in .NET
My preference towards JSON is that I find it easier to read, if I am having to debug data, and javascript likes it.
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
|
|
|
|
|
Yeah, an XML file can be expected to be well-formed, but that's not necessarily the case with CSV, HTML, and JSON.
What drives me nuts about XML is namespaces -- they're best avoided in most cases.
|
|
|
|
|
Not to forget that XML has been around since the 1970s, and JSON was only described in the early 2000s by Douglas Crockford et al.
So in the meantime, A LOT of applications went with XML as the default for exchanging data.
-- Peter.
|
|
|
|
|
Good point, it also seems to have taken a long time after 2000 for devs to trust using JSON.
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
|
|
|
|
|
|
I agree, it really is so much better than XML.
|
|
|
|
|
I first read that as "I am coming to seriously love JSOP" !!
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
