|
Aha the top left of the mail app!! Goody Delete not as fatal as I thought, still a stupid place for the button though!
|
|
|
|
|
My sincere suggestion to you is: adopt two greyhounds. Your morning routine will not proceed until theirs is fairly complete: pet, feed, pet, put outside for the morning constitutional, [sneak make the coffee in here], bring dogs in, pet, get dressed, pet, pet, [dammit I have to go to work], pet, grab keys, go back and pour coffee in thermos, pet, escape out side door.
Software Zen: delete this;
|
|
|
|
|
I can barely care for myself, giving me added responsibilty is not the way to go!
|
|
|
|
|
Dan Terminus - Margaritifer[^]
I've been listening to this album for three weeks now.
Spotify recommended it to me and I was drawn to it by the colorful psychedelic album cover.
The music isn't all that psychedelic though.
It's synthwave, or retrowave, basically meaning it has it's roots in 80's synth music.
I'm not a fan of 80's music, but if it was necessary to come to this I'm glad we've had it
|
|
|
|
|
|
Zardonic's been a while!
I used to listen to this stuff in high school, some 10+ years ago (and as I'm typing this hell yeah!)
|
|
|
|
|
No wonder … this is catchy and heavy at the same time, hopefully is the whole album like this. But … in the past days i also listened to some quiet music (latest Tool album from last SOTW) - so far I found 1st and last track quite amazing… ,
Cheers
|
|
|
|
|
I've been listening to Tool a few times too.
So far I find it rather long
The album has some very good parts though.
|
|
|
|
|
It sounds like "Bride of Pin-Bot" on steroids
I could definitively not listen for that for three weeks; I admire your stamina.
while (!(success = Try()));
|
|
|
|
|
phil.o wrote: Bride of Pin-Bot The what now?
phil.o wrote: I could definitively not listen for that for three weeks; I admire your stamina. Well, not three weeks straight, but like once a day or for the last week once every two days or so
|
|
|
|
|
|
That sounds like the SOTW on tranquilizers
|
|
|
|
|
Exactly
"Five fruits and vegetables a day? What a joke!
Personally, after the third watermelon, I'm full."
|
|
|
|
|
no thank you. it's just noise to me.
I do like techno, EDM, etc. but this is just crap IMHO.
|
|
|
|
|
|
|
Nice ones!
Not quite my current mood (yet ), but I do love such stuff from time to time.
|
|
|
|
|
|
It's a torrid affair. I've begun using JSON to back entity objects and after doing so I don't think I'm ever going back.
Jeez it's cool tho.
I'm addicted. Maybe I need help.
This is just exciting.
At the risk of dropping some code here:
an example of one (read-only in this case, but adding writing is doable too)
public abstract class TmdbEntity : IEquatable<TmdbEntity>
{
protected TmdbEntity(IDictionary<string, object> json)
{
Json = json ?? throw new ArgumentNullException(nameof(json));
}
public IDictionary<string, object> Json { get; protected set; }
protected T GetField<T>(string name,T @default=default(T))
{
object o;
if (Json.TryGetValue(name, out o) && o is T)
return (T)o;
return @default;
}
public bool Equals(TmdbEntity rhs)
{
if (ReferenceEquals(this, rhs))
return true;
if (ReferenceEquals(rhs, null))
return false;
return ReferenceEquals(Json, rhs.Json);
}
public override bool Equals(object obj)
{
return Equals(obj as TmdbEntity);
}
public static bool operator==(TmdbEntity lhs, TmdbEntity rhs)
{
return lhs.Equals(rhs);
}
public static bool operator!=(TmdbEntity lhs, TmdbEntity rhs)
{
return !lhs.Equals(rhs);
}
public override int GetHashCode()
{
var jo = Json as JsonObject;
if(null!=jo)
{
jo.BaseDictionary.GetHashCode();
}
return Json.GetHashCode();
}
}
Then in your derived classes:
public class TmdbLanguage : TmdbEntity
{
public TmdbLanguage(IDictionary<string,object> json) : base(json)
{
}
public string Name => GetField<string>("name");
public string EnglishName => GetField<string>("english_name");
public string Iso => GetField<string>("iso_639_1");
}
Then on any entity you can also get the Json property to get all of the actual data for your object as one unit, which you can then query on. This makes it better than traditional entities that consume and toss or otherwise hide the underlying data structure, frankly. It's not only more "pure" to back your state with the actual data you got, it's also easier to query on it or update it. By query it i mean do like "JsonObject.Select(myEntity.Json,"$.id")" if you want or "myEntity.Id"
So, do I need help?
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
|
|
|
|
|
honey the codewitch wrote: So, do I need help? Yes, definitively
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
okay true, but what i've just done is either a really Good Idea(TM) or a really Bad Idea(TM)
either way, it's cool. Simple, elegant, unobtrusive. But using that many dictionary instances might freak some people out.
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
|
|
|
|
|
honey the codewitch wrote: but what i've just done is either a really Good Idea(TM) or a really Bad Idea(TM)
It's actually quite possible to be both at the same time. It all depends on what problems you encounter, or DON'T encounter further down the road.
It's only experience that can tell you what problems you don't encounter.
Personally, unstructured data gives me the shivers.
|
|
|
|
|
Jörgen Andersson wrote: Personally, unstructured data gives me the shivers.
Well, to be fair, JSON is not entirely unstructured, but it is a bit fast and loose.
I've been using it for this TMDb thing i made and hitting it pretty hard just now, and it rocks.
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
|
|
|
|
|
JSON works well where traditional relation databases lacks. Tree structures.
|
|
|
|
|
that too yeah, but as far as indexing tree structures, i mean, XML can build trees too. It's just that xml isn't implicitly indexed when using most tools.
If you store JSON objects as dictionaries like most programming environments do (using whatever their associative array mechanism is) then their keys are automatically indexed which makes pathfinding through the tree much faster.
makes sense to me. Just use IDs as field names and bob's your uncle.
so i agree.
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
|
|
|
|